Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL)
-
None
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
-
MDEV-12791 Default value of rocksdb_datadir not ideal
- Closed
- relates to
-
MDEV-12451 SHOW DATABASES shows #mysql50#.rocksdb
- Closed
-
MDEV-13505 mysql_upgrade failed with rocksdb
- Closed
-
MDEV-14461 Connect + RocksDB
- Closed