ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.1.0-rc1026
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2026-11-09
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The test verifies that replica set write blocking remains enabled after a primary re-election. Currently, the test created a three-node replica set without specifying member priorities. The DSC passthrough assigns priority 1 to the initial primary and priority 0 to standby nodes. Because priority-0 members cannot become primary, the planned stepdown failed: neither standby was an eligible replacement. The test therefore never reached its post-election write-blocking checks.

      As part of this ticket, we have to explicitly configure all three members with priority 1 and await replication before stepping down. This makes replacement primaries electable and ensures they have applied the write-block state before the handoff. Once this is done, we have to add the test to no_passthrough_disagg_override_replsets.

            Assignee:
            Anna Maria Nestorov
            Reporter:
            Anna Maria Nestorov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: