[SERVER-80206] Semaphore ticket holder does not respect interruptibility when timeout is less than 500ms Created: 17/Aug/23 Updated: 22/Aug/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
When waiting to acquire a ticket, the semaphore ticket holder uses an internal interval of 500ms. However, if the timeout provided by the caller is less than this interval and is not able to acquire the ticket within that time, we immediately return instead of checking for interrupt first. Note that this differs from the behavior of the priority ticket holder which always checks for interrupt after waiting. |
| Comments |
| Comment by Haley Connelly [ 22/Aug/23 ] |
|
This was put on the backlog because eventually the PriorityTicketHolder should be supported on all platforms (SERVER-74082, SERVER-72616) and the SemaphoreTicketHolder will be removed. |