Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-21927

RocksDB: Failed to get column family flags from cf, SIGABRT in myrocks::Rdb_drop_index_thread::run

    XMLWordPrintable

Details

    Description

      INSTALL SONAME 'ha_rocksdb';
       
      CREATE TABLE t1 (pk INT PRIMARY KEY, a INT) ENGINE=RocksDB;
      INSERT INTO t1 VALUES (1,1),(2,1);
       
      --error ER_DUP_ENTRY
      ALTER TABLE t1 ADD UNIQUE (a) COMMENT 'foo';
      CREATE TABLE t2 (b INT) ENGINE=RocksDB;
      DROP TABLE t2;
      

      10.4 b7362d5f

      2020-03-12 18:50:02 0 [ERROR] RocksDB: Failed to get column family flags from cf id 2. MyRocks data dictionary may get corrupted.
      200312 18:50:02 [ERROR] mysqld got signal 6 ;
       
      #3  <signal handler called>
      #4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
      #5  0x00007fd12e0a142a in __GI_abort () at abort.c:89
      #6  0x00007fd0d3638976 in myrocks::Rdb_drop_index_thread::run (this=0x7fd0d3feb5e0 <myrocks::rdb_drop_idx_thread>) at /data/src/10.4/storage/rocksdb/ha_rocksdb.cc:11604
      #7  0x00007fd0d36e5206 in myrocks::Rdb_thread::thread_func (thread_ptr=0x7fd0d3feb5e0 <myrocks::rdb_drop_idx_thread>) at /data/src/10.4/storage/rocksdb/rdb_threads.cc:34
      #8  0x00007fd1300214a4 in start_thread (arg=0x7fd0bb7f6700) at pthread_create.c:456
      #9  0x00007fd12e155d0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
      

      Reproducible on 10.2-10.5, debug and non-debug alike.
      Stack traces may vary, and SIGABRT can happen in a thread other than 1st.

      Attachments

        Activity

          People

            psergei Sergei Petrunia
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.