The issue is fixed for versions after v4.2 by SERVER-42374. We should apply the same reordering to v4.2 to prevent the periodic runner from addressing TimestampMonitor members after their destruction.
- is related to
-
SERVER-42374 TimestampMonitor should stop its PeriodicJob prior to destructing itself
- Closed