[SERVER-40586] step up instead of stepping down in stepdown suites Created: 11/Apr/19  Updated: 29/Oct/23  Resolved: 07/May/19

Status: Closed
Project: Core Server
Component/s: Replication, Sharding, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.1.11

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: prepare_testing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
related to SERVER-40594 Range deleter in prepare conflict ret... Closed
related to SERVER-40700 Deadlock between read prepare conflic... Closed
is related to SERVER-38188 Create split brain passthroughs Backlog
Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-04-22, Repl 2019-05-06, Repl 2019-05-20
Participants:
Linked BF Score: 8

 Description   

This is being pulled out of SERVER-38188. Stepping up instead of stepping down still leads to stepdowns, but leads to unconditional stepdowns which are unretryable and could surface more interesting deadlocks.

We will keep the election timeout at 24 hours, step up a node, and then after a few seconds the original primary will step down when it sees a higher term. We may want to adjust the heartbeat interval to tune the length of time with 2 primaries.



 Comments   
Comment by Githook User [ 07/May/19 ]

Author:

{'email': 'lingzhi.deng@mongodb.com', 'name': 'Lingzhi Deng', 'username': 'ldennis'}

Message: SERVER-40586: Step up instead of stepping down in stepdown suites
Branch: master
https://github.com/mongodb/mongo/commit/c1e677229fb0c816fd4b2ea243f6127ce78b74bf

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