-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
Affects Version/s: 2.7.7
-
Component/s: Concurrency, Storage
-
None
-
Fully Compatible
-
ALL
-
v3.4
-
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