|Category 1||Category 2|
|Failure due to operating error||Definition file settings do not match the contents in the database file.||[Server]: 7036, 160012, 160013
[Description] (Number of partition groups discrepancy)
[Format] Number of partition groups in the definition file number, number of partition groups in the database file
Check the value of /dataStore/concurrency in gs_node.json.
When recovering from a backup, check that the settings match those at the time of the backup (/configInfo/groupNum in gs_backup_info.json).
|[Server]: 68024, 160018
[Contents] (Number of partitions inconsistent)
[Format] Number of partitions in the definition file, number of partitions in the database file
|Check the value of /dataStore/partitionNum in gs_cluster.json.
When recovering from a backup, check that the settings match those at the time of the backup (/configInfo/partitionNum in gs_backup_info.json).
|[Server]: 68026, 68064
[Contents] (Block size inconsistent)
[Format] Block size of definition file, block size of database file
|Check the value of dataStore/storeBlockSize in gs_cluster.json.
Check whether the value is the same as actualFileSize in the event log (block size of database file).
|File required for recovery does not exist||[Server]: 20004 to 20008
[Contents] (Necessary file check error)
[Format] Insufficient but confirmed file contents
|Check whether all the files have been copied when starting from a backup ("gs_restore --test", etc.).
See the “GridDB backup guide” for details regarding backup.
|Failure due to internal error||A failure to continue has occurred during the recovery process||[Server]: 20009
[Contents] (Internal error)
[Format] Based on tracing at the point the error is detected
|Check with support services. If a backup exists, recovery using the data is also possible.|