[SERVER-28326] Wait for primary to stabilize in initial_sync4.js test after node is added to 1 node replica set Created: 15/Mar/17  Updated: 05/Sep/18  Resolved: 04/May/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.4.6, 3.5.7

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-37010 Prevent unexpected elections in initi... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: Repl 2017-05-08
Participants:
Linked BF Score: 1

 Description   

The test starts with a 1 node replica set then adds a second node and expects the original node to stay primary throughout, which isn't actually guaranteed.



 Comments   
Comment by Githook User [ 16/Jun/17 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-28326 Ensure primary doesn't change in initial_sync4.js test

(cherry picked from commit d6524fe73938fbce2c9c429886e425363aa40a9c)
Branch: v3.4
https://github.com/mongodb/mongo/commit/dab240e80f5f69df8f7c5796146fa0fed876a84d

Comment by Githook User [ 04/May/17 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-28326 Ensure primary doesn't change in initial_sync4.js test
Branch: master
https://github.com/mongodb/mongo/commit/d6524fe73938fbce2c9c429886e425363aa40a9c

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