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

RocksDB engine fails to upgrade from 10.4.12 to 10.4.13

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.4.13, 10.5.3
    • 10.4, 10.5
    • None
    • Official Docker image (Ubuntu 18.04)

    Description

      Upgrading MariaDB (and its MyRocks plugin) from 10.4.12 to 10.4.13 results in the RocksDB engine failing to load:

      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [Warning] RocksDB: Schema mismatch - A .frm file exists for table [redacted], but that table is not registered in RocksDB
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [Warning] RocksDB: Schema mismatch - A .frm file exists for table [redacted], but that table is not registered in RocksDB
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [Warning] RocksDB: Schema mismatch - A .frm file exists for table [redacted], but that table is not registered in RocksDB
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [Warning] RocksDB: Schema mismatch - A .frm file exists for table [redacted], but that table is not registered in RocksDB
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [Warning] RocksDB: Schema mismatch - A .frm file exists for table [redacted], but that table is not registered in RocksDB
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [Warning] RocksDB: Schema mismatch - A .frm file exists for table [redacted], but that table is not registered in RocksDB
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [Warning] RocksDB: Schema mismatch - A .frm file exists for table [redacted], but that table is not registered in RocksDB
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [Warning] RocksDB: Schema mismatch - A .frm file exists for table [redacted], but that table is not registered in RocksDB
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [Warning] RocksDB: Schema mismatch - A .frm file exists for table [redacted], but that table is not registered in RocksDB
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [Warning] RocksDB: Schema mismatch - A .frm file exists for table [redacted], but that table is not registered in RocksDB
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [ERROR] RocksDB: Problems validating data dictionary against .frm files, exiting
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [ERROR] RocksDB: Failed to initialize DDL manager.
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [ERROR] Plugin 'ROCKSDB' init function returned error.
      mariadb-ssd_1           | 2020-05-17 19:29:46 0 [ERROR] Plugin 'ROCKSDB' registration as a STORAGE ENGINE failed.
      

      Setting rocksdb_validate_tables=0 as a possible workaround results in this:

      mariadb-ssd_1           | 2020-05-17 19:31:52 0 [ERROR] RocksDB: Table_store load error, Status Code: 2, Status: Corruption: ZSTD not supported or corrupted ZSTD compressed block contents
      mariadb-ssd_1           | 2020-05-17 19:31:52 0 [ERROR] RocksDB: Failed to initialize DDL manager.
      mariadb-ssd_1           | 2020-05-17 19:31:52 0 [ERROR] Plugin 'ROCKSDB' init function returned error.
      mariadb-ssd_1           | 2020-05-17 19:31:52 0 [ERROR] Plugin 'ROCKSDB' registration as a STORAGE ENGINE failed.
      

      This was all done on the official MariaDB Docker image (Ubuntu Bionic) with the mariadb-plugin-rocksdb also installed.

      It may also be relevant that I have five other column families in MyRocks besides the default column family, each with their own RocksDB options.

      Attachments

        Issue Links

          Activity

            People

              psergei Sergei Petrunia
              asun Andrew Sun
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.