Fix potential std::terminate in MovePrimaryCoordinator

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.0.2, 9.1.0-rc1022, 9.0.3
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v9.0, v8.3
    • CAR Team 2026-09-14
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      (copilot)
      _runImpl is noexcept, but this newly hoisted operation-context setup now runs before an ExecutorFuture can capture failures. makeOperationContext() applies forwardable metadata (including token parsing) and is not noexcept; if it throws, the process calls std::terminate instead of returning an error to the coordinator retry machinery. Keep the same-shard check in an initial future continuation, with a branch/helper that skips the remaining workflow on a no-op, so all throwing work stays inside the future chain.

            Assignee:
            Wolfee Farkas
            Reporter:
            Wolfee Farkas
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: