Fix false positive MisplacedCollection during config.system.sessions creation

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2026-07-20
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      During CreateCollectionCoordinator, the collection is created locally on the first data shard before config.collections is updated. checkMetadataConsistency compares local vs catalog state, finds a local-only collection on a shard that is not the config DB primary (config server), and _checkLocalInconsistencies reports MisplacedCollection with no sessions-specific exemption.

      The coordinator runs on the first data shard and holds the DDL lock there, while CMC holds the DDL lock on the config server, so the two do not serialize, and this race produces a false positive.

            Assignee:
            Pol Pinol
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: