[SERVER-27056] Don't enforce data freshness for step-up command Created: 16/Nov/16  Updated: 05/Apr/17  Resolved: 19/Dec/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.4.2, 3.5.2

Type: Bug Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Jack Mulrow
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-27148 StepUp command should take over prima... Closed
Related
related to SERVER-27461 Retry connecting to shut down primary... Closed
is related to SERVER-26748 Don't call for priority takeover when... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4
Sprint: Repl 2017-01-23
Participants:
Linked BF Score: 0

 Description   

We don't run priority takeover if the node is not within 2 seconds with the most up-to-date member. This behavior affects step-up command as well. We should skip the check for step-up command.



 Comments   
Comment by Githook User [ 28/Dec/16 ]

Author:

{u'username': u'jsmulrow', u'name': u'Jack Mulrow', u'email': u'jack.mulrow@mongodb.com'}

Message: SERVER-27056 Don't enforce data freshness for stepUp command

(cherry picked from commit d5a000950a8c1802138d50d9313a721b4c7c4c1c)
Branch: v3.4
https://github.com/mongodb/mongo/commit/68c98261efff90d55ebae2678e4b30c0d888cac8

Comment by Githook User [ 19/Dec/16 ]

Author:

{u'name': u'Jack Mulrow', u'email': u'jack.mulrow@mongodb.com'}

Message: SERVER-27056 Don't enforce data freshness for stepUp command
Branch: master
https://github.com/mongodb/mongo/commit/d5a000950a8c1802138d50d9313a721b4c7c4c1c

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