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

Report lastAppliedAndJournaledOptime in replSetGetStatus

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Minor Change

      Description

      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?

        Attachments

          Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-23287 Cleanup replSetGetStatus output/code (field names)

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-22336 Report committedOptime in replSetGetStatus

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-22276 implement "j" flag in write concern apply to secondary as well as primary

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              scotthernandez Scott Hernandez
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: