-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Catalog, Index Maintenance, Storage
-
Fully Compatible
-
Storage NYC 2019-04-22, Storage NYC 2019-05-06
-
10
-
13
Ensure that no places rely on database intent locks to ensure a Collection pointer renames valid.
Check that collection drop doesn't block on open transactions involving other collections in the same database.
- is depended on by
-
SERVER-37988 recover locks on step up at the beginning of the state transition rather than at the end
- Closed
-
SERVER-39518 Only use collection MODE_X locks for collection rename
- Closed
- is duplicated by
-
SERVER-38140 Only acquire a Database IX lock for replicated collection drops
- Closed
- related to
-
SERVER-40971 Fix the check of _resolvedNss in AutoGetCollection
- Closed
-
SERVER-41426 StorageInterface's dropCollection should only take Database IX lock
- Closed