[SERVER-26830] Randomize priority takeover timeout Created: 28/Oct/16  Updated: 05/Apr/17  Resolved: 02/Mar/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.4.4, 3.5.4

Type: Improvement Priority: Major - P3
Reporter: Siyuan Zhou Assignee: William Schultz (Inactive)
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: Repl 2017-02-13, Repl 2017-03-06
Participants:

 Description   

We do not apply any random offset to the priority takeover election timeout. This means that if two nodes with the same priority discover that a lower priority primary at about the same time, they have an increased chance of both running for takeover election, both losing, and putting the system back into the "scramble to find any primary" behavior. This might then allow the low-priority node to get re-elected as primary, restarting the process.



 Comments   
Comment by Githook User [ 03/Apr/17 ]

Author:

{u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'}

Message: SERVER-26830 Randomize priority takeover delay

(cherry picked from commit aa8987a0d92c06c900579c5d38e814cd0647a2d5)
Branch: v3.4
https://github.com/mongodb/mongo/commit/76ba81f3eb29b1d88330b92ccf269cdf753fe58c

Comment by Githook User [ 02/Mar/17 ]

Author:

{u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'}

Message: SERVER-26830 Randomize priority takeover delay
Branch: master
https://github.com/mongodb/mongo/commit/aa8987a0d92c06c900579c5d38e814cd0647a2d5

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