-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Metadata
-
None
-
Storage Engines, Storage Engines - Persistence
-
None
-
None
After creating a database with checkpoint_threads specified, WiredTiger writes it to WiredTiger.basecfg. Opening the database with an older version of WT that does not support this parameter then results in:
[1776106369:411752][325733:0x735aa21e56c0], wt, wiredtiger_open: [WT_VERB_DEFAULT][ERROR]: int __config_check_search(WT_SESSION_IMPL *, const WT_CONFIG_CHECK *, u_int, const WT_CONFIG_ITEM *, const uint8_t *, const WT_CONFIG_CHECK **), 114: unknown configuration key 'checkpoint_threads': Invalid argument wt: WT_TRY_SALVAGE: database corruption detected Note: this issue typically arises from running wt util in an incorrect directory or not specifying one. Ensure you execute wt within a WiredTiger directory, or use the -h flag to direct it to one.
However, there is arguably no reason to preserve this parameter, as it only affects runtime state. As such, this config parameter can be stripped away in __conn_write_base_config.