Multi-collection locking must only succeed on the DB primary

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Catalog and Routing
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: