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

Report readConcernMajorityOpTime in replSetGetStatus

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Sharding 10 (02/19/16)

      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.

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

              Created:
              Updated:
              Resolved: