[SERVER-29536] apply_batch_only_goes_forward.js should be configured to use 2 electable nodes instead of 3 Created: 09/Jun/17  Updated: 30/Oct/23  Resolved: 12/Jun/17

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

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Repl 2017-06-19
Participants:
Linked BF Score: 0

 Description   

After restarting the initial primary node with a modified minValid, one of the remaining electable nodes will step up as primary. Occasional network slowness may result in a primary change between the 2 remaining electable nodes. We can configure this test to use 2 electable nodes (third node will be an arbiter) to eliminate the possibility of an election during this phase of the test.



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

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-29536 reduce number of data-bearing nodes in apply_batch_only_goes_forward.js from 3 to 2

(cherry picked from commit 49c02153a4996e61bf5c3e35398eb30397e8ae01)
Branch: v3.4
https://github.com/mongodb/mongo/commit/04130f4b62a52b6c40d216fb57055738562ce53c

Comment by Githook User [ 12/Jun/17 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-29536 reduce number of data-bearing nodes in apply_batch_only_goes_forward.js from 3 to 2
Branch: master
https://github.com/mongodb/mongo/commit/49c02153a4996e61bf5c3e35398eb30397e8ae01

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