ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      Upgrade: previous DSC release at fleet FCV X -> next release at FCV X -> setFCV Y. Rollback: setFCV X on the new release -> binary rollback to the previous release, on the same data.

      No DSC test covers the last step: the previous release restarting on data that the new release wrote, including state written while the FCV was Y and still present after setFCV X. The new binary tolerates that state, so every existing suite passes. The old binary may fail to start or crash.

      Existing coverage covers only parts of the flow:

      • SERVER-132286, SERVER-132288 and SERVER-118573 cycle the FCV on a single binary. Validation runs on the newer binary, which tolerates leftovers.
      • disagg_repl_jscore_passthrough_multiversion_last_patch_{new_old,old_new} and SERVER-138389 mix binaries at a fixed FCV. There is no setFCV and no restart onto another binary.
      • The format matrix (SPM-4838) only restores older snapshots on the current binary.
      • SERVER-129277 (Backlog) swaps the binary in place, but at a fixed FCV.
      • jstests/multiVersion/genericSetFCVUsage/fcv_core/do_upgrade_downgrade.js runs this sequence for classic replica sets only: last-lts/last-continuous, plain ReplSetTest, and no "start on old binary" phase.

      Precedents:

      • HELP-91146: rollback from 8.3.0-rc1004 to rc1003 failed to start because of an oplog format change.

      Scope

      The test can be similar to jstests/multiVersion/genericSetFCVUsage/fcv_core/do_upgrade_downgrade.js.
      Possible scenario:

      • we start with binary = 9.0,  FCV = 9.0
      • upgrade binaries: binary = 9.1, FCV = 9.0
      • setFCV 9.1: binary = 9.1, FCV = 9.1
      • setFCV 9.0: binary = 9.1, FCV = 9.0; in this step, some metadata can be left behind; the 9.1 binary is tolerant to read that metadata
      • downgrade binaries: binary = 9.0, FCV = 9.0;  the 9.0 binary doesn't understand the metadata, and crashes

            Assignee:
            Unassigned
            Reporter:
            Igor Praznik
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: