-
Type: Bug
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Concurrency, Storage
-
None
-
Storage Execution
-
ALL
One assumption for the RAII database lock types was that destruction order is always the reverse of construction order. However, with increasing usage of unique_ptr and boost::optional for more dynamic locking, we need additional checking that locking semantics are not violated.
- related to
-
SERVER-30371 Separate renameCollection across DB commands into individual oplog entries
- Closed