[DOCS-13643] Investigate changes in SERVER-47453: Maintain a rolling list of timestamps of when the last sync source changes occurred Created: 12/May/20  Updated: 13/Nov/23  Resolved: 11/Aug/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.7.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Dave Cuthbert (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-47453 Maintain a rolling list of timestamps... Closed
Participants:
Days since reply: 2 years, 26 weeks ago
Epic Link: DOCSP-15042

 Description   

Description

Downstream Change Summary

Added a new server parameter called maxNumSyncSourceChangesPerHour that provides the value for how many sync source changes can happen per hour before the node temporarily turns off re-evaluating a sync source. The default value is 3.

Description of Linked Ticket

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).

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 11/Aug/21 ]

Author:

{'name': 'Dave Cuthbert', 'email': 'dave.cuthbert@mongodb.com', 'username': 'davemungo'}

Message: DOCS-13643 add timestamp setting parameter v5.0
Branch: master
https://github.com/mongodb/docs/commit/bad6b3c19b2420293872993d4f6f6b21244bdb14

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