[SERVER-42234] Make txn_two_phase_commit_failover.js robust to all replica nodes running for election at the same time Created: 15/Jul/19  Updated: 29/Oct/23  Resolved: 27/Aug/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.2.1, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Lamont Nelson
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-43002 txn_two_phase_commit_failover.js shou... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Sharding 2019-08-12, Sharding 2019-08-26, Sharding 2019-09-09
Participants:
Linked BF Score: 9

 Description   

The test repeatedly induces failovers on the coordinator shard. Currently, it's possible for all three nodes to run for election and therefore refuse to vote for anyone but themselves, and mongos times out after waiting for 20 seconds for the coordinator shard to have a primary.

One idea is to only make two of the three replica nodes in the coordinator shard electable. The third replica node should then act as an "arbiter" in elections and vote for one of the other two.



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

Author:

{'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi'}

Message: SERVER-42234: make one node not able to assume primary role

(cherry picked from commit 823a293c05984fac564be0e7c1cfbf461dcd1ab4)
Branch: v4.2
https://github.com/mongodb/mongo/commit/a46c2c1a6f69206b2b15f9e2ac366968bd966d54

Comment by Githook User [ 27/Aug/19 ]

Author:

{'name': 'Lamont Nelson', 'email': 'lamont.nelson@mongodb.com', 'username': 'lamontnelson'}

Message: SERVER-42234: make one node not able to assume primary role
Branch: master
https://github.com/mongodb/mongo/commit/823a293c05984fac564be0e7c1cfbf461dcd1ab4

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