-
Type:
Engineering Test
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
QE 2024-04-01, QE 2024-04-15, QE 2024-04-29, QE 2024-05-13, QE 2024-05-27, QE 2024-06-10, QE 2024-06-24, QE 2024-07-08, QE 2024-07-22, QE 2024-08-05, QE 2024-08-19, QE 2024-09-02, QE 2024-09-16, QE 2024-09-30, QE 2024-10-14, QE 2024-10-28
When commands aren't interruptible for a significant period of time (either due to explicitly making themselves uninterruptible or by not calling checkForInterrupt) it both can block replication elections and also hinders our ability to schedule operations effectively. We don't have a good way today to catch areas of the code that aren't sufficiently interruptible.
- is related to
-
SERVER-86504 Better observability for operations which exceed yielding and interrupt deadlines
-
- In Progress
-
- related to
-
SERVER-72258 Audit and add missing checkForInterrupt to SBE stages
-
- Closed
-