Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.4.2, 3.5.2
Affects Version/s: None
Component/s: Replication
Labels:
- neweng

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v3.4
Sprint:
Repl 2017-01-23
Linked BF Score:
0
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

is duplicated by

SERVER-27148 StepUp command should take over primary even if repl lagged

Closed

is related to

SERVER-26748 Don't call for priority takeover when repl lagged

Closed

related to

SERVER-27461 Retry connecting to shut down primary until failure in shutdown_primary.js

Closed

Assignee:: Jack Mulrow
Reporter:: Siyuan Zhou
Participants:: Githook User, Jack Mulrow, Siyuan Zhou
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Nov 16 2016 12:13:55 AM UTC
Updated:: Apr 05 2017 11:42:39 AM UTC
Resolved:: Dec 19 2016 07:28:07 PM UTC
Confidence Status Last Update:: 13/Dec/16 9:31 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates