-
Type: New Feature
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Catalog, Concurrency
-
None
-
Fully Compatible
-
Execution Team 2019-12-02, Execution Team 2019-12-16
-
22
After SERVER-43859, index creation that necessitates implicit collection creation should only require MODE_IX locks. This ticket should remove any remaining acquisition of locks in this code path other than those. In particular, createIndexes::getOrCreateDatabase should go away.
Ideally, implicit collection creation via index creation can comprise a single oplog entry and be treated similarly to explicit collection creation with indexes attached.
- is depended on by
-
SERVER-44849 Allow createIndexes inside multi-document transactions if on an empty collection created in the same transaction or on a non-existing collection
- Closed
- is duplicated by
-
SERVER-40952 Release the DB X lock in createIndexes after creating the collection/database
- Closed
- related to
-
SERVER-49415 create_new_indexes_with_conflict.js hangs intermittently due to unreliable log line checking
- Closed
-
SERVER-49837 add test for createIndexes command to check if all indexes already exist under an intent lock
- Closed