[SERVER-62358] Test that new yielding behavior is used on eligible queries Created: 04/Jan/22 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Sprint: | Execution Team 2022-01-24, Execution Team 2022-06-27 |
| Participants: |
| Description |
|
We should add a test which checks that the new yielding code path is actually taken, for queries that are eligible. One way to do this may be to add a fail point which sets the 'msg' flag on CurOp. Alternatively, we may want to have a CurOp or explain flag indicating which yielding behavior was used. |