StaleConfig error handling in shard_role.cpp should not wait for critical section without check session back in

XMLWordPrintableJSON

    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2025-07-07
    • 200
    • None
    • 3
    • TBD
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      If the StaleConfig is caused by a resharding critical section, waiting without checking the session back in could make resharding oplog application get stuck trying to check out the session that got checked out when applying oplog entries in the same session as the operation that is stuck waiting for resharding critical section to complete.

              Assignee:
              Jordi Serra Torrens
              Reporter:
              Cheahuychou Mao
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: