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

Report readConcernMajorityOpTime in replSetGetStatus

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.2
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 10 (02/19/16)

      Description

      Currently we report the optime of each node in the replicaset and the lastCommittedOpTime of the primary, but we don't report the readConcernMajorityOpTime of a node if it's the primary. The lastCommittedOpTime can refer to the optime of operations that don't actually exist a secondary reporting replSetGetStatus. This should refer to the OpTime used for readConcern: Majority calls, (the committed snapshot OpTime) that exists on the reporting node. If readConcern is turned off, this field should be omitted.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              judah.schvimer Judah Schvimer
              Reporter:
              judah.schvimer Judah Schvimer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: