Playbook to anticipate & mitigate potential stuck setFCV (8.x → 9.0) during authoritative shard cloning

XMLWordPrintableJSON

    • Catalog and Routing
    • CAR Team 2026-08-03, CAR Team 2026-08-17, CAR Team 2026-08-31
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is a placeholder/playbook ticket, not a confirmed bug report.

      Its purpose is to proactively anticipate and prepare for potential (currently unknown) issues where a setFCV upgrade from 8.x to 9.0 could get stuck during authoritative shards cloning.

            Assignee:
            Aitor Esteve Alvarado
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: