-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 8.1.0-rc0
-
Component/s: None
-
None
-
Storage Execution
-
ALL
-
Storage Execution 2025-04-14
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The changes in SERVER-101001 made it so we try to open history store cursors on WiredTiger, potentially before we are allowed to do so. When this happens, WiredTiger returns an error, however, WiredTiger also logs an error message:
2025-03-14T13:44:18.016+01:00 E WT 22435 [S] [ftdc] "WiredTiger error message","attr":{"error":22,"message":{"ts_sec":1741956258,"ts_usec":15488,"thread":"732:140722956099216","session_name":"WT_SESSION.open_cursor","category":"WT_VERB_DEFAULT","category_id":12,"verbose_level":"ERROR","verbose_level_id":-3,"msg":"int __cdecl __session_open_cursor(struct __wt_session *,const char *,struct __wt_cursor *,const char *,struct __wt_cursor **):816:cannot open a non-statistics cursor before connection is opened","error_str":"Invalid argument","error_code":22}}
These log messages could be noisy and misleading unless we can suppress them somehow.
I think we can hook into the mdb_handle_error callback to have the calling thread ignore any errors when collecting history store statistics.
- is caused by
-
SERVER-101001 Expose additional metrics about history store
-
- Closed
-