Authoritative metadata cloning DDL should clone to shards that only owned chunks historically

XMLWordPrintableJSON

    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v9.0
    • CAR Team 2026-07-20, CAR Team 2026-08-03
    • 200
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      The authoritative_metadata_on_FCV_transition.js test is not currently running on v9.0/master because of the issue described in SERVER-128742 / DEVPROD-34823.

       

      If the test is re-enabled it is failing on this assertion, the failure started after SERVER-130698.

       

      The problem appears to be that:

      1. We move a chunk from shard0 to shard1 non-auhoritatively.
      2. We upgrade the FCV to 9.0, this does the cloning.
      3. We check shard0's authoritative metadata is consistent.
        1. We find that shard0 historically had a chunk, so we expect the collection entry to be present.
        2. However starting at SERVER-130698 we only broadcast the cloning to shards that currently own chunks, so we don't find it.

       

      This ticket should investigate/fix the issue and re-enable the test.

       

      –

      Investigation result: The test is correct and it reveals a bug where authoritative metadata cloning DDL is missing cloning to shards that historically owned chunks. The fix is done in this ticket.

            Assignee:
            Joan Bruguera Micó
            Reporter:
            Joan Bruguera Micó
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: