[SERVER-34478] Make shards in concurrency suite not able to reelect primary Created: 13/Apr/18  Updated: 06/Dec/22  Resolved: 16/Apr/18

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

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-31972 Reduce the number of iterations for t... Closed
Assigned Teams:
Sharding
Operating System: ALL
Participants:
Linked BF Score: 26

 Description   

BF-7458 manifests as a spontaneous reelection of primary during a database operation between tests such as checkUUIDsConsistentAcrossCluster (which cache primary host name).
This reelection is not expected by the tests and hence causes them to fail.
There are 2 possible solutions assuming that reelections are normal and can happen due to heartbeat delay.
1. look into all failing cases and use the current primary when making requests.
2. configure the sharded cluster in a way that reelection will choose the same primary.


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