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

Test rocksdb.add_index_inplace_sstfilewriter failing due to max_num_locks limit

    Details

    • Type: Bug
    • Status: Done
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: 5.7.21-20
    • Fix Version/s: 5.7.21-21
    • Component/s: MyRocks
    • Labels:

      Description

      rocksdb.add_index_inplace_sstfilewriter  w4 [ fail ]
              Test ended at 2018-02-26 07:51:22
      
      CURRENT_TEST: rocksdb.add_index_inplace_sstfilewriter
      mysqltest: At line 62: query 'ALTER TABLE t1 ADD INDEX kb_copy(b), ALGORITHM=COPY' failed: 12014: Status error 10 received from RocksDB: Operation aborted: Failed to acquire lock due to max_num_locks limit
      
      The result from queries just before the failure was:
      CREATE TABLE t1(pk CHAR(5) PRIMARY KEY, a char(30), b char(30)) ENGINE=ROCKSDB COLLATE 'latin1_bin';
      set rocksdb_bulk_load=1;
      set rocksdb_bulk_load_size=100000;
      LOAD DATA INFILE <input_file> INTO TABLE t1;
      set rocksdb_bulk_load=0;
      select count(pk) from t1;
      count(pk)
      3000000
      select count(a) from t1;
      count(a)
      3000000
      select count(b) from t1;
      count(b)
      3000000
      ALTER TABLE t1 ADD INDEX kb(b), ALGORITHM=INPLACE;
      safe_process[25187]: Child process: 25189, exit: 1
      
      
      
      Server [mysqld.1 - pid: 25074, winpid: 25074] log: 
      Server log from this test:
      ----------SERVER LOG START-----------
      2018-02-26T07:45:28.839782Z 6 [Note] RocksDB: Begin index creation (0,362)
      ----------SERVER LOG END-------------
      

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                george.lorch George Lorch
                Reporter:
                laurynas.biveinis Laurynas Biveinis (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 hour, 30 minutes
                  1h 30m