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

Docs for SERVER-33546: Add numeric syncing field to replSetGetStatus members array

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.0-rc0, 3.6.6, 3.4.16
    • None

    Description

      Description:

      replSetGetStatus.members[n]. syncSourceId is a new field which displays the member id of replSetGetStatus.members[n].syncSourceHost.

      Scope of changes:

      • replSetGetStatus
        • add new field
        • update sample output
        • top level "syncSourceId"
      • 4.0.txt
      • 4.0-compatibility

      Impact to other docs outside of this product:

      MVP:

      Resources:

      Engineering Ticket Description:

      An important consideration in debugging issues in the field is which members are syncing from which. It is currently difficult to obtain the history of this and correlate it with other events because this information is currently only available as a string field, which is not preserved as a metric in FTDC.

      It would be helpful if the members array had a numeric field which is the _id of the current sync source for that member, or -1 if it has no sync source.

      (It is currently possible, but difficult, to obtain this information fro FTDC from the full reference documents stored once per chunk: due to SERVER-27230, when there is a change of sync source typically we also start a new chunk. Once SERVER-27230 is fixed, it will then be impossible to obtain accurate information about changes of sync source from FTDC.)

      Attachments

        Issue Links

          Activity

            People

              kay.kim@mongodb.com Kay Kim (Inactive)
              kay.kim@mongodb.com Kay Kim (Inactive)
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                4 years, 2 weeks, 1 day ago