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

Add millisecond-granularity wallclock times for the various metrics in replSetGetStatus's optimes subdocument

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • v4.0, v3.6
    • Repl 2018-11-05, Storage NYC 2019-02-25, Storage NYC 2019-03-11
    • 5

      The response to replSetGetStatus includes a subdocument named optimes, which contains the OpTime for various important oplog events, including lastCommittedOpTime, readConcernMajorityOpTime, appliedOpTime and durableOpTime. As of MongoDB 3.6, the actual oplog entries corresponding to these OpTimes have a wall clock time with milliseconds resolution recorded in them. We should extend replSetGetStatus to report the wall clock times corresponding to these optimes, so that we can (usually) get millisecond-granularity measurements of replication lag and back-to-back majority read-modify-write latencies.

      The work for this ticket is split into SERVER-40080, SERVER-40078, and SERVER-40353. SERVER-34598 is an umbrella ticket with no work items.

            Assignee:
            maria.vankeulen@mongodb.com Maria van Keulen
            Reporter:
            schwerin@mongodb.com Andy Schwerin
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: