StaleConfig failures originating from applyOps command do not trigger sharding metadata recovery

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2025-08-04, CAR Team 2025-08-18, CAR Team 2025-09-29
    • 2
    • None
    • 3
    • TBD
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      Shards handle StaleConfig exceptions indicating that the shard needs to recover its knowledge of the sharding metadata by triggering the recovery process on the ServiceEntryPoint. However, this is not happening for applyOps command.

      This is because applyOps failure do not manifest neither as an exception bubbling up all the way to the ServiceEntryPoint, nor applyOps sets the OperationShardingState::setShardingOperationFailedStatus.

              Assignee:
              Pol Pinol
              Reporter:
              Jordi Serra Torrens
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: