Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13643

Investigate changes in SERVER-47453: Maintain a rolling list of timestamps of when the last sync source changes occurred

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.7.0
    • manual, Server
    • None

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

      Attachments

        Issue Links

          Activity

            People

              dave.cuthbert@mongodb.com Dave Cuthbert
              backlog-server-pm Backlog - Core Eng Program Management Team
              Dave Cuthbert Dave Cuthbert
              Samyukta Lanka
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                1 year ago