Report lastAppliedAndJournaledOptime in replSetGetStatus

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • Minor Change
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Now (as of SERVER-22276) that we are keeping track of the both the lastApplied and lastAppliedAndJournaled OpTimes we should expose them for use.

      Open question: Are they needed yet, or is this just for reporting/diagnostics?

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: