Details
-
Improvement
-
Resolution: Won't Fix
-
Major - P3
-
None
-
3.1.7
-
None
-
Storage Execution
-
QuInt B (11/02/15)
Description
In order to avoid potential deadlocks, we require consistent ordering of lock acquisition/release. Currently there are no checks for these, and it is easy to accidentally introduce incorrect orderings. Moreover, there is a possibility that some of these can be extremely rare, potentially leading to deadlock.
By checking lock ordering in debug builds, we can reduce the likelihood of such problems.
Attachments
Issue Links
- is depended on by
-
SERVER-18410 Remove RWLock
-
- Closed
-