-
Type: Task
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Not Applicable
-
Storage Engines
-
5
-
Nick - 2024-04-30, Megabat - 2024-05-14, 2024-05-28 - FOLLOW ON SPRINT
Filing this ticket to catalog follow-on work for investigating a HELP ticket where the mongod shutdown process took a long time (4 mins).
The information available around the time of shutdown doesn't provide enough conclusive evidence and we have seen this behaviour twice now. The scope of this ticket should be focused on attempting to repro this behaviour and identify a root cause.
This could include writing a test to test eviction + checkpoint followed by a shutdown call.
- is related to
-
WT-12125 Create an Atlas Log Ingestion rule for WT startup and shutdown timing
- Closed