Force checkpoint past FCV transition in multiversion tests that do their own replica set setup

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • Repl 2026-08-17
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-131892 made ReplSetTest.initiate() force a checkpoint past the FCV transition, so that a node running an older binary that joins a set declared mixed-version up front cannot initial sync a checkpoint predating that transition.

      Tests that perform their own mixed-version setup were missed. They start an all-latest set, run setFeatureCompatibilityVersion to the downgrade FCV themselves, and only then add a node on older binary + reInitiate(). The new node initial syncs its sync source's last checkpoint; if that checkpoint predates the FCV transition, the new node observes an FCV state its binary cannot interpret and fails early in initial sync. The set then never reaches a healthy state and the test times out.

       

            Assignee:
            Moustafa Maher
            Reporter:
            Moustafa Maher
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: