Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
Fully Compatible
-
Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03
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.
Attachments
Issue Links
- related to
-
SERVER-69461 The behaviour of lock acquisitions differs depending on whether OpContext or Locker is used
-
- Closed
-