-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.1.11
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.2
-
Repl 2019-06-17, Repl 2019-07-01, Repl 2019-07-15, Repl 2019-07-29, Repl 2019-08-12, Repl 2019-08-26, Repl 2019-09-09
The rollback_after_enabling_majority_reads.js test runs a final rollback here after restarting node 0 with EMRC=true. It intends for the rollback to occur on node 0, but since node 0 is a SECONDARY at the time it is restarted with EMRC=true, the RollbackTest fixture will end up running the rollback on node 1. We should consider shutting down and restarting node 1 to let node 0 become primary again before initiating the final rollback sequence.
- related to
-
SERVER-41218 rollback_after_enabling_majority_reads.js test should ensure the correct primary before restarting other nodes [v4.0]
- Closed