[SERVER-47601] Investigate defaults for changeSyncSourceThresholdMillis and maxNumSyncSourceChangesPerHour server parameters Created: 16/Apr/20  Updated: 08/Dec/23  Resolved: 25/Feb/21

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

Type: Task Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Evin Roesle
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-47447 Add server parameter for the ping tim... Closed
is related to SERVER-47448 Add a server parameter for the max nu... Closed
Participants:

 Description   

We should use the data we get from the metrics in replSetGetStatus for ping time between nodes and the metrics in server status for how often we choose a new sync source to evaluate the defaults we have chosen for the changeSyncSourceThresholdMillis and maxNumSyncSourceChangesPerHour server parameters.



 Comments   
Comment by Alan Zheng [ 07/Dec/23 ]

evin.roesle@mongodb.com samy.lanka@mongodb.com Was there a reason why changeSyncSourceThresholdMillis was never publically documented? 

Comment by Steven Vannelli [ 25/Feb/21 ]

Samy chatted with Evin and they agreed the existing defaults are sufficient.

Comment by Samyukta Lanka [ 28/May/20 ]

Taking this out of the Periodically Re-evaluate Sync Source project as discussed. Flagging for scheduling so we don't lose track of this ticket.

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