Loading...

XML

Word

Printable

JSON

Consider a PSA set in config C0.
We then reconfig to C1 where the "S" node has votes:0.
The "S" node goes down and falls behind as the Primary accepts and commits many writes.
The "S" node restarts.
Now the DBA reconfigures the "S" node to have votes:1 again in C2.
The "S" node gets elected with the arbiter's vote, but without all of the writes the original primary committed while "S" was down.

depends on

SERVER-60217 [v5.0] enableReconfigRollbackCommittedWritesCheck should be applied on 4.4

is depended on by

SERVER-56670 Ensure reconfig cannot roll back committed writes in replica sets with multiple arbiters

is related to

SERVER-56481 Update TLA+ spec for reconfig to model arbiters

related to

MONGOSH-891 Add check for PSA set in reconfigForPSASet()

MONGOSH-702 Create a shell helper to reconfig from a PA to a PSA set

SERVER-56801 Update placeholder links for the reconfig check in PSA sets

SERVER-56919 Add validation for memberIndex to reconfigToPSASet() shell helper

(2 related to)