Uploaded image for project: 'Percona Server'
  1. Percona Server
  2. PS-5029

RocksDB - vague error message "Operation aborted: Failed to acquire lock due to max_num_locks limit"

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: On Hold
    • Priority: Low
    • Resolution: Unresolved
    • Affects Version/s: 8.0.12-2rc1, 5.7.23-24
    • Fix Version/s: None
    • Component/s: MyRocks

      Description

      I was altering a table and got this:

      8.0.12>alter table sbtest1 engine=rocksdb;
      ERROR 1296 (HY000): Got error 10 'Operation aborted: Failed to acquire lock due to max_num_locks limit' from ROCKSDB
      

      This would be fine if "max_num_locks" variable would exist:

      8.0.12>show variables like '%max_num_locks%';
      Empty set (0.00 sec)
      

      Instead it seems that "max_num_locks" is related to

      8.0.12>show variables like '%row_locks%';
      +-----------------------+---------+
      | Variable_name         | Value   |
      +-----------------------+---------+
      | rocksdb_max_row_locks | 1048576 |
      +-----------------------+---------+
      1 row in set (0.00 sec)
      
      8.0.12>set session rocksdb_max_row_locks=4000000;
      Query OK, 0 rows affected (0.00 sec)
      
      8.0.12>alter table sbtest1 engine=rocksdb;
      Query OK, 3000000 rows affected (1 min 10.89 sec)
      Records: 3000000  Duplicates: 0  Warnings: 0
      

      This is not 8.0 specific and I am unaware if "max_num_locks" is somehow related to some other variables also, but if this is not the case then I propose to correct the message and point the user straight to "rocksdb_max_row_locks".

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                george.lorch George Lorch
                Reporter:
                tomislav.plavcic@percona.com Tomislav Plavcic
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - Not Specified
                  Not Specified
                  Logged:
                  Time Spent - 35 minutes
                  35m