-
Type: Improvement
-
Resolution: Done
-
Priority: Critical - P2
-
Affects Version/s: None
-
Component/s: Diagnostics
-
Minor Change
-
v5.0
-
Security 2021-09-06, Security 2021-09-20, Security 2021-10-04, Security 2021-10-18
-
(copied to CRM)
-
133
Currently diagnostic data collection does not begin until fairly late in the startup sequence, after some potentially significant activity such as oplog stones and interrupted index builds have been done, so it can't be used to diagnose problems early in the startup sequence. Ideally it should be started as early as possible; one dependency is storage engine initialization since it collects WT internal statistics that won't be available until the storage engine is initialized, so maybe it could go right after storage engine initialization.
- is related to
-
SERVER-48221 Shut down ftdc after storage engine
- Closed
- related to
-
WT-9373 Allow MongoDB to access WT stats during open and shutdown
- Closed