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

Check the cluster cardinality parameter before tracking and moving a collection

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Critical - P2 Critical - P2
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2024-04-01, CAR Team 2024-04-15

      We are relying on the direct shard connection checks to prevent data loss due to direct connections when moving unsharded collections. However, this parameter is not set atomically with adding a second shard. In order to guarantee that there are no more direct shard operations happening when a collection is moved, we should check the cluster cardinality parameter in the moveCollection command before tracking the collection.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: