[SERVER-76683] Remove use of initiateWithShortElectionTimeout from shard split tests that do not need to use it Created: 28/Apr/23  Updated: 29/Oct/23  Resolved: 01/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 10

 Description   

Various shard split tests currently use initiateWithShortElectionTimeout and do not actually need it. The use of this flag can trigger frequent elections on an artificially/unrealistically short timeout that can cause shard split tests to be aborted. This isn't buying us anything in terms of correctness/resiliency testing.

An earlier work-in-progress incarnation of shard split seems to have relied on election timeouts to step up a primary on the recipient cluster after a split. As such, initiateWithShortElectionTimeout was introduced to speed up some shard split tests. Now that shard split uses replSetStepUp to request that a recipient primary steps up after reconfig, this short election timeout is no longer necessary. Additionally, evergreen sets electionTimeoutMillis to 24 hours (86400000 ms) to avoid unnecessary elections, so we can safely use the default for shard split.



 Comments   
Comment by Githook User [ 01/May/23 ]

Author:

{'name': 'Christopher Caplinger', 'email': 'christopher.caplinger@mongodb.com', 'username': 'UnicodeSnowman'}

Message: SERVER-76683: Remove use of short election timeout in shard split tests
Branch: master
https://github.com/mongodb/mongo/commit/8953737584fbcf79988dc6c7e49dad760f86d89d

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