[SERVER-25291] Rethink the default timeout of primary catch-up Created: 26/Jul/16  Updated: 06/Dec/22  Resolved: 04/Nov/16

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

Type: Improvement Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

In SERVER-23663, we introduce catch-up phase after a node becoming primary. The time period that a new primary waits for to catch up its oplog is 5 seconds by default. We may want to tune the number.



 Comments   
Comment by Spencer Brody (Inactive) [ 27/Jul/16 ]

Specifically we may want to consider making the default value a function of the election and/or heartbeat timeouts

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