[SERVER-44678] Make txn_two_phase_commit_failover.js robust to it taking a long time for a new coordinator primary to be elected Created: 15/Nov/19  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.3 Desired

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: sharding-wfbf-sprint
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-41314 txn_two_phase_commit_failover.js is n... Open
Assigned Teams:
Cluster Scalability
Operating System: ALL
Sprint: Sharding 2020-01-13, Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06
Participants:
Linked BF Score: 0

 Description   

The test currently usesĀ force stepdown (which means the stepdown will occur even if there is no electable secondary that is caught up, and that the current primary will not do an election handoff).

This means it is possible that no secondary will run for election for 10 seconds, which cuts it close to theĀ 20 seconds mongos waits to find a new primary.


Generated at Thu Feb 08 05:06:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.