[SERVER-70010] Stop using getKillStatus to check for OperationContext interruption. Created: 27/Sep/22 Updated: 30/Jan/24 Resolved: 03/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Diener (Inactive) | Assignee: | Matt Diener (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Sprint: | Service Arch 2022-10-03, Service Arch 2022-10-17 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
`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 |
| Comments |
| Comment by Matt Diener (Inactive) [ 03/Oct/22 ] |
|
Backwards compatibility is dependent on the changes that went in before this. Estimated to be fairly minor if such changes are necessary. |
| Comment by Githook User [ 03/Oct/22 ] |
|
Author: {'name': 'Matt Diener', 'email': 'matt.diener@mongodb.com', 'username': 'mattdiener'}Message: |
| Comment by Githook User [ 03/Oct/22 ] |
|
Author: {'name': 'Matt Diener', 'email': 'matt.diener@mongodb.com', 'username': 'mattdiener'}Message: |
| Comment by Githook User [ 03/Oct/22 ] |
|
Author: {'name': 'Matt Diener', 'email': 'matt.diener@mongodb.com', 'username': 'mattdiener'}Message: |