The distributed lock is preventing overlaps between the critical section acquired by migrations and rename coordinators. As there is a plan to get rid of the distributed lock, purpose of this ticket is to acquire the critical section for the target collection only in case it is not sharded.
This is fine because SERVER-67325 introduced the acquisition of the critical section to avoid concurrent collections creation, but if a collection is already sharded that cannot happen.
- causes
-
SERVER-73385 RenameCollectionCoordinator wrongly releases critical section for destination ns.
-
- Closed
-
- related to
-
-
- Closed
-