[SERVER-15781] reenable replsetprio1.js Created: 22/Oct/14  Updated: 19/Nov/14  Resolved: 27/Oct/14

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

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

We need to make the test more resilient to election races between nodes of different priorities; and to consider how to ensure higher priority nodes win their elections over lower priority nodes. This could involve changing how the election sleep time affects veto power.



 Comments   
Comment by Githook User [ 27/Oct/14 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-15781 Separate the concepts of next electable time and step-down until in replication.

The topology coordinator needs to track two distinct notions of a node not being
willing to stand for election. The first is that of the step-down period.
During the step down period, the node will not stand for election due to the
step-down command being issued. In heartbeat responses, nodes in the step down
period should report that they are not electable.

The second notion is that of the post election sleep period. If a node loses an
election, it declines to stand again for a brief period of time (1 second plus a
random interval), to avert problems related to ties. During this period, its
heartbeat responses should still report the node is electable, to suppress the
election of lower priority nodes.
Branch: master
https://github.com/mongodb/mongo/commit/07c0c80e190206b8e6f037a885bc5971a78cae3e

Generated at Thu Feb 08 03:38:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.