-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Minor Change
-
ALL
-
Service Arch 2022-10-03, Service Arch 2022-10-17
`getKillStatus` captures a subset of the situations under which an OperationContext may be interrupted. It should almost never be used outside of the SA code base.
We provided incorrect guidance for tasks logged under SERVER-56251, and those should be addressed ASAP.
Additionally, a quick look should be done in other places to ensure `getKillStatus` is not being used inappropriately.
This is being done in lieu of SERVER-69496, to avoid changing internal implementation details of OperationContext `kill`.
- is depended on by
-
SERVER-69496 InterruptedAtShutdown can be thrown without the operation context being marked as killed
- Closed
- related to
-
SERVER-56251 Alleviate problems that arise when OperationContext::markKilled is called with a non-Interruption error
- Backlog
-
SERVER-85912 Audit code paths explicitly checking for ErrorCodes::Interrupted
- Backlog