[SERVER-67015] Investigate circumstances under which we wait while holding locks Created: 03/Jun/22 Updated: 29/Jun/22 Resolved: 29/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Louis Williams |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Execution Team 2022-06-27, Execution Team 2022-07-11 | ||||||||
| Participants: | |||||||||
| Description |
|
If we wait for another task to complete while holding locks/tickets, this could lead to ticket exhaustion and/or deadlock. To test where we do this, we could try adding an assertion to waitForConditionOrInterrupt to ensure we are not holding locks. If it turns out we violate this assertion, we should try to get an understanding of the circumstances. |
| Comments |
| Comment by Louis Williams [ 29/Jun/22 ] |
|
Closing as Won't Do and pointing to the discussion in |