[SERVER-41218] rollback_after_enabling_majority_reads.js test should ensure the correct primary before restarting other nodes [v4.0] Created: 17/May/19  Updated: 29/Oct/23  Resolved: 04/Sep/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.0.9
Fix Version/s: 4.0.13

Type: Bug Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-41221 rollback_after_enabling_majority_read... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: 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
Participants:
Linked BF Score: 36

 Description   

The rollback_after_enabling_majority_reads.js test expects node 0 to become primary here, by shutting down and restarting node 1. This may not always work if node 1 restarts and wins an election too soon. We should make this test wait for node 0 to become primary in this case before node 1 is restarted or is allowed to get elected.



 Comments   
Comment by Githook User [ 04/Sep/19 ]

Author:

{'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}

Message: SERVER-41218 rollback_after_enabling_majority_reads.js test should
ensure that the final rollback occurs on node 0
Branch: v4.0
https://github.com/mongodb/mongo/commit/00664a874fb31909684f8e8c85c7091d4d8b7e8f

Comment by William Schultz (Inactive) [ 04/Sep/19 ]

When running a patch build for these changes it looks like I ran into the bug that appeared in BF-14323.

Generated at Thu Feb 08 04:57:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.