Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-53017

replSetGetStatus remainingInitialSyncEstimatedMillis always 0

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.9.0, 4.4.3
    • None
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Repl 2020-12-14

    Description

      This is related to the new metrics in SERVER-47863.

      After calling db.adminCommand({ replSetGetStatus: 1, initialSync: 1 }).initialSyncStatus.remainingInitialSyncEstimatedMillis, sometimes this will return a value before data starts copying, but once data begins to copy the value is always 0.

      Tested on mongod-4.9.0-alpha-596-g4437864

      Attachments

        Issue Links

          Activity

            People

              jason.chan@mongodb.com Jason Chan
              alex.bevilacqua@mongodb.com Alex Bevilacqua
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: