[SERVER-47453] Maintain a rolling list of timestamps of when the last sync source changes occurred Created: 10/Apr/20  Updated: 29/Oct/23  Resolved: 12/May/20

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

Type: Task Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Samyukta Lanka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-47454 Stop re-evaluating sync source if max... Closed
Documented
is documented by DOCS-13643 Investigate changes in SERVER-47453: ... Closed
Duplicate
is duplicated by SERVER-47448 Add a server parameter for the max nu... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-05-04, Repl 2020-05-18
Participants:

 Description   

The list should contain at most maxNumSyncSourceChangesPerHour number of entries. It will be updated every time a sync source change happens (not just those caused by re-evaluating a node's sync source after fetching a batch of oplog entries).



 Comments   
Comment by Githook User [ 12/May/20 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-47453 Maintain a rolling list of timestamps of the when the recent sync source changes occurred
Branch: master
https://github.com/mongodb/mongo/commit/ab9233d37298a13752ebed493c2c2f973b087adf

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