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

.rocksdb folder may break workflow which re-create data directory

Details

    Description

      I did see many workflows/scripts which re-create data directory with commands like:

      sudo rm -rf /var/lib/mysql/*
      		 
      sudo mysql_install_db

      OR :

      sudo rm -rf /var/lib/mysql/*
      		 
      cp -R /backup-location/* /var/lib/mysql/

      The rm command will not clean up eventual .rocksdb folder, which may cause errors in new instance like:

      2017-10-25 10:12:40 139671395502272 [Warning] RocksDB: Schema mismatch - Table d9.b is registered in RocksDB but does not have a .frm file
      		 
      2017-10-25 10:12:40 139671395502272 [ERROR] RocksDB: Problems validating data dictionary against .frm files, exiting
      		 
      2017-10-25 10:12:40 139671395502272 [ERROR] RocksDB: Failed to initialize DDL manager.
      		 
      2017-10-25 10:12:40 139671395502272 [ERROR] Plugin 'ROCKSDB' init function returned error.
      		 
      2017-10-25 10:12:40 139671395502272 [ERROR] Plugin 'ROCKSDB' registration as a STORAGE ENGINE failed.

      Attachments

        Issue Links

          duplicates

          Task - A task that needs to be done. MDEV-12791 Default value of rocksdb_datadir not ideal

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-12451 SHOW DATABASES shows #mysql50#.rocksdb

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13505 mysql_upgrade failed with rocksdb

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14461 Connect + RocksDB

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            anikitin Andrii Nikitin (Inactive) created issue -
            elenst Elena Stepanova made changes -
            Field Original Value New Value
            elenst Elena Stepanova made changes -
            anikitin Andrii Nikitin (Inactive) made changes -
            Description I did see many workflows/scripts which re-create data directory with commands like:

            {code:bash}
            sudo rm -rf /var/lib/mysql/*
            sudo mysql_install_db
            {code}
            The rm command will not clean up eventual .rocksdb folder, which may cause errors in new instance like:

            {noformat}
            2017-10-25 10:12:40 139671395502272 [Warning] RocksDB: Schema mismatch - Table d9.b is registered in RocksDB but does not have a .frm file
            2017-10-25 10:12:40 139671395502272 [ERROR] RocksDB: Problems validating data dictionary against .frm files, exiting
            2017-10-25 10:12:40 139671395502272 [ERROR] RocksDB: Failed to initialize DDL manager.
            2017-10-25 10:12:40 139671395502272 [ERROR] Plugin 'ROCKSDB' init function returned error.
            2017-10-25 10:12:40 139671395502272 [ERROR] Plugin 'ROCKSDB' registration as a STORAGE ENGINE failed.
            {noformat}


             
            		I did see many workflows/scripts which re-create data directory with commands like:

            {code:bash}
            sudo rm -rf /var/lib/mysql/*
            sudo mysql_install_db
            {code}

            OR :
            {code:bash}
            sudo rm -rf /var/lib/mysql/*
            cp /backup-location/* /var/lib/mysql/
            {code}

            The rm command will not clean up eventual .rocksdb folder, which may cause errors in new instance like:

            {noformat}
            2017-10-25 10:12:40 139671395502272 [Warning] RocksDB: Schema mismatch - Table d9.b is registered in RocksDB but does not have a .frm file
            2017-10-25 10:12:40 139671395502272 [ERROR] RocksDB: Problems validating data dictionary against .frm files, exiting
            2017-10-25 10:12:40 139671395502272 [ERROR] RocksDB: Failed to initialize DDL manager.
            2017-10-25 10:12:40 139671395502272 [ERROR] Plugin 'ROCKSDB' init function returned error.
            2017-10-25 10:12:40 139671395502272 [ERROR] Plugin 'ROCKSDB' registration as a STORAGE ENGINE failed.
            {noformat}


             
            anikitin Andrii Nikitin (Inactive) made changes -
            Description I did see many workflows/scripts which re-create data directory with commands like:

            {code:bash}
            sudo rm -rf /var/lib/mysql/*
            sudo mysql_install_db
            {code}

            OR :
            {code:bash}
            sudo rm -rf /var/lib/mysql/*
            cp /backup-location/* /var/lib/mysql/
            {code}

            The rm command will not clean up eventual .rocksdb folder, which may cause errors in new instance like:

            {noformat}
            2017-10-25 10:12:40 139671395502272 [Warning] RocksDB: Schema mismatch - Table d9.b is registered in RocksDB but does not have a .frm file
            2017-10-25 10:12:40 139671395502272 [ERROR] RocksDB: Problems validating data dictionary against .frm files, exiting
            2017-10-25 10:12:40 139671395502272 [ERROR] RocksDB: Failed to initialize DDL manager.
            2017-10-25 10:12:40 139671395502272 [ERROR] Plugin 'ROCKSDB' init function returned error.
            2017-10-25 10:12:40 139671395502272 [ERROR] Plugin 'ROCKSDB' registration as a STORAGE ENGINE failed.
            {noformat}


             
            		I did see many workflows/scripts which re-create data directory with commands like:

            {code:bash}
            sudo rm -rf /var/lib/mysql/*
            sudo mysql_install_db
            {code}

            OR :
            {code:bash}
            sudo rm -rf /var/lib/mysql/*
            cp -R /backup-location/* /var/lib/mysql/
            {code}

            The rm command will not clean up eventual .rocksdb folder, which may cause errors in new instance like:

            {noformat}
            2017-10-25 10:12:40 139671395502272 [Warning] RocksDB: Schema mismatch - Table d9.b is registered in RocksDB but does not have a .frm file
            2017-10-25 10:12:40 139671395502272 [ERROR] RocksDB: Problems validating data dictionary against .frm files, exiting
            2017-10-25 10:12:40 139671395502272 [ERROR] RocksDB: Failed to initialize DDL manager.
            2017-10-25 10:12:40 139671395502272 [ERROR] Plugin 'ROCKSDB' init function returned error.
            2017-10-25 10:12:40 139671395502272 [ERROR] Plugin 'ROCKSDB' registration as a STORAGE ENGINE failed.
            {noformat}


             
            anikitin Andrii Nikitin (Inactive) made changes -
            psergei Sergei Petrunia made changes -
            psergei Sergei Petrunia made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            psergei Sergei Petrunia made changes -
            Fix Version/s 10.2.12 [ 22810 ]
            Fix Version/s 10.2 [ 14601 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 83139 ] MariaDB v4 [ 153022 ]

            People

              psergei Sergei Petrunia
              anikitin Andrii Nikitin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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