-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Catalog and Routing
-
ALL
The multi-collection locking capability is only safe to use if run on the DB primary. Otherwise it is nonsensical, since for a sharded collection with chunks on the non-DB primary shard, there will be no entries for the side collections.
Because of this, the multi-collection locking capability should ensure (after taking the DB lock) that the primary is on the same collection.
- depends on
-
SERVER-78724 Integrate acquisitions into aggregations
- Open
-
SERVER-77507 Integrate acquisitions into Find
- Closed
- has to be done after
-
SERVER-66869 Get rid of the multi DB locking capability
- Closed