-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Server Integration
-
ALL
-
SESINEXT 2026-12-01
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The MongoDB wiredTigerExtraDiagnostics validator is out of sync with WiredTiger’s current extra_diagnostics options.
SPM-2897 added wiredtiger asserts to mongodb from 7.0. However, Wiredtiger has renamed their options in the import 713b8810e0f1 as part of WT-10439 Update diagnostic categories.
Valid WiredTiger options now are rejected by MongoDB.
WiredTiger valid extra_diagnostics:
Config('extra_diagnostics', '[]', r'''
enable additional diagnostics in WiredTiger. These additional diagnostics include
diagnostic assertions that can cause WiredTiger to abort when an invalid state
is detected.
Options are given as a list, such as
<code>"extra_diagnostics=[out_of_order,visibility]"</code>.
Choosing \c all enables all assertions. When WiredTiger is compiled with
\c HAVE_DIAGNOSTIC=1 all assertions are enabled and cannot be reconfigured
''',
type='list', choices=[
"all", "checkpoint_validate", "cursor_check", "disk_validate", "eviction_check",
"generation_check", "hs_validate", "key_out_of_order", "log_validate", "prepared",
"slow_operation", "txn_visibility"]),
Server's WT global options:
Status validateExtraDiagnostics(const std::vector<std::string>& value, const boost::optional<TenantId>& tenantId) { try { std::set<std::string> flagArr = {"all", "concurrent_access", "data_validation", "invalid_op", "out_of_order", "panic", "slow_operation", "visibility"};
We should update the flagArr and description to match WiredTiger’s current option list and add a test to detect future drift between MongoDB and WiredTiger. Since this bug exists in older versions, we may need to backport the fix up to 7.0.