Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-66871

Multi-collection locking must only succeed on the DB primary

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 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.

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: