[SERVER-69727] Make ResourceLock acquisitions in the PersistentTaskQueue interruptible Created: 15/Sep/22 Updated: 29/Oct/23 Resolved: 22/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2144-Milestone-0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, the PersistentTaskQueue uses the non-interruptible ResourceMutex acquisition. There is no real problem with it since these mutexes should never be contended, but it prevents us from removing the non-interruptible (Locker-only) constructor of ResourceLock. This ticket is to switch it to use the interruptible (OpContext) one. |
| Comments |
| Comment by Githook User [ 21/Sep/22 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |