Report committedOptime in replSetGetStatus

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 3.3.2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Sharding 10 (02/19/16), Repl F (01/29/16)
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently we report the optime of each node in the replicaset but we don't report the committedOptime. This can be put at the top of the reporting information.

              Assignee:
              Judah Schvimer
              Reporter:
              Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: