[SERVER-66871] Multi-collection locking must only succeed on the DB primary Created: 31/May/22 Updated: 26/Oct/23 |
|
| Status: | Blocked |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | PM-2144-QW-Fallout, oldshardingemea | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
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. |