Prevent StaleConfig error in placement_conflict_time.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.0.1, 9.0.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v9.0
    • CAR Team 2026-08-17, CAR Team 2026-08-31
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This createCollection command can abort the transaction and throw StaleConfig if the CollectionMetadata is unknown, which is guaranteed by this point. Most of the time, it doesn't throw because mongoS retries transparently as it's the first statement in the transaction, but that requires `otherDb`'s primary shard to be different from `dbName`'s, otherwise it would be the second statement in the transaction (the first being this dummy operation).

            Assignee:
            Aitor Esteve Alvarado
            Reporter:
            Aitor Esteve Alvarado
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: