-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Execution Team 2021-07-26, Execution Team 2021-08-09, Execution Team 2021-08-23
-
5
The TimestampMonitor currently checks and reports Interruption as it is processing its listeners. We have observed in our CI system that the server crashes when we have an exception type that is not handled by the current PeriodicJob task.
It would be useful to include an additional exception handling loop for non-Interruption types and handle these exceptions appropriately.
- related to
-
SERVER-59575 fix log ID in TimestampMonitor
- Closed