-
Type:
Bug
-
Status: Closed
-
Priority:
Minor - P4
-
Resolution: Fixed
-
Affects Version/s: 2.7.7
-
Component/s: Concurrency, Storage
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Operating System:ALL
-
Backport Requested:v3.4
-
Sprint:Storage 2017-07-31
Probelm:
See https://github.com/mongodb/mongo/blob/master/src/mongo/db/commands/rename_collection.cpp#L113
Lock::GlobalWrite globalWriteLock(txn->lockState());
|
Solution:
Scope this lock as a DB_X when renaming within a database. Renaming between databases probably still requires a G_X or perhaps two DB_X locks.
- is depended on by
-
SERVER-30037 Fix replset timeouts with collectionUUIDs enabled
-
- Closed
-
-
SERVER-30087 convertToCapped should not yield locks before renaming
-
- Closed
-
- is documented by
-
DOCS-10528 Docs for SERVER-15723: Avoid G_X lock for rename_collection within database
-
- Resolved
-
- is related to
-
DOCS-10992 convertToCapped is missing the 'global write lock' warning
-
- Resolved
-