[SERVER-26848] Exit catchup mode when not syncing more data - MongoDB Jira

XML

Word

Printable

Details

Type: Task
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.4.6, 3.5.7
Component/s: Replication
Labels:
None

Backwards Compatibility:
Minor Change
Backport Requested:

v3.4
Sprint:
Repl 2017-01-23, Repl 2017-02-13, Repl 2017-03-06, Repl 2017-03-27, Repl 2017-04-17, Repl 2017-05-08
Linked BF Score:
0

Description

Currently we expose one parameter to the replica set config - catchUpTimeoutMillis (defaults to 2 seconds) - which controls how long to stay in catchup mode after winning an election.

We should exit catchup mode when the primary finds itself the most up-to-date after refreshing heaertbeats.

Attachments

Issue Links

is related to

SERVER-28969 Wait until the voter has the latest optime in case 3 of catchup.js

Closed

SERVER-26847 Tie threshold of how caught up we must be to call for priority takeover to the catchup timeout

Closed

related to

SERVER-27499 Race condition in SyncSourceResolver shutdown

Backlog

SERVER-28751 Allow stepDown command to work against primary in catchup mode

Closed

Activity

People

Assignee:: Siyuan Zhou

Reporter:: Spencer Brody (Inactive)

Participants:: Githook User, Siyuan Zhou, Spencer Brody

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: Oct 31 2016 06:02:32 PM UTC

Updated:: May 10 2018 05:26:52 PM UTC

Resolved:: Apr 21 2017 02:49:46 AM UTC