[SERVER-86164] Create a test that catches operations that aren't interruptible for significant periods of time Created: 02/Feb/24 Updated: 07/Feb/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Engineering Test | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
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. |
| Comments |
| Comment by Louis Williams [ 06/Feb/24 ] |
|
We (StorEx) believe that the lack of interrupt checking is mostly a problem that applies to the Query system. We have a project already to address the interruptibility with storage engine operations, PM-3546, but the problem needs to be evaluated more holistically in the query system. |