Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
In some cases error avoids to let RocksDB start.
In this cases the only options is to restore a full backup , even if
the error is not critical like
[ERROR] RocksDB: Could not get index information for Index Number, (x,x) , table tablename
[ERROR] RocksDB: Failed to initialize DDL mananger
[ERROR] Plugin 'ROCKSDBĂ„ init function returned error.
So in some cases there should be a possibility to skip the error.
Suggestion:
Add variable
rocksdb_ignore_error
Simple Version wood be a boolean, maybe it makes also sense to create a ENUM for different error types.
Certainly default should be 0 or 'NONE'
Ok, the variable is named rocksdb_ignore_datadic_errors.
It can be only set as a server argument or in my.cnf.
).
Setting rocksdb_ignore_datadic_errors=1 will make the plugin to try to continue when seeing a class of MyRocks data dictionary errors that were experienced by the customer. (Note that this is NOT all kinds of errors. It is only "index definition is missing" error that can occur when a pre-10.6 server crashes in the middle of a DDL, as well as startup sanity check failure