Empty list of shards persisted to the placement history if the rename must retry the update TXN

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: 9.0.0-rc0
    • Component/s: Change streams, Sharding
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2026-07-06
    • 200
    • 馃煡 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      When updating the placement history during a rename, the list of shards is std::move'd into the transaction callback. If the first TXN attempt gets aborted, in the callback the second retry will see and persist an empty list of shards (since the original one has been moved out).

        1. repro-SERVER-130182.patch
          3 kB
          Joan Bruguera Mic贸

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

              Created:
              Updated:
              Resolved: