Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
v4.4, v4.2
-
Execution Team 2020-06-29, Execution Team 2020-07-13, Execution Team 2020-07-27, Execution Team 2020-09-21, Execution Team 2020-10-05, Execution Team 2020-11-16
Description
We've encountered cases of issues in WT shutdown like WT-6164 where diagnosis was difficult (and likely impossible in the field) because ftdc is shut down before the storage engine. We should move ftdc shutdown after storage engine shutdown.
Attachments
Issue Links
- is related to
-
SERVER-52815 Investigate calling 'rollback_to_stable' prior to shutting down WiredTiger
-
- Backlog
-
- related to
-
SERVER-58026 Omitted FTDC sections cause frequent schema changes that limit FTDC retention
-
- Backlog
-
-
SERVER-59065 CatalogStats uses unsafe CollectionCatalog pointer during startup
-
- Closed
-
-
SERVER-25042 Start diagnostic data collection as early as possible
-
- Closed
-
-
SERVER-27692 Can diagnostic data capture be stopped later in the shutdown process?
-
- Closed
-
-
SERVER-54472 Collect additional FTDC metrics during shutdown for replica sets
-
- Closed
-