-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We mark operations as interrupted in many different situations (like during step down, rollback, etc) and rely on the operations to quickly check that they have been interrupted to let the system make progress. However, we have seen many situations where operations take a very long time (over 30 seconds) to notice they need to be interrupted. We should track how long it takes for an operation to check that it has been interrupted so that we can identify which operations are not adhering to our timing requirements.
- duplicates
-
-
- Closed
-
- is related to
-
SERVER-106466 Track the time between when an operation was marked killed and when it actually was killed
-
- Closed
-
-
SERVER-108656 Log operation deadline in slow query logs
-
- Needs Scheduling
-
- related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Needs Scheduling
-