[SERVER-22445] Report readConcernMajorityOpTime in replSetGetStatus Created: 02/Feb/16  Updated: 14/Mar/17  Resolved: 09/Feb/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.3.2

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-19867 Do not read directly from collections... Closed
Documented
is documented by DOCS-7123 Report readConcernMajorityOpTime in R... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 10 (02/19/16)
Participants:

 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.



 Comments   
Comment by Githook User [ 09/Feb/16 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-22445 report readConcernMajorityOpTime in ReplSetGetStatus
Branch: master
https://github.com/mongodb/mongo/commit/8a58e2fb57806c0ccd415773d490167e783941bf

Generated at Thu Feb 08 04:00:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.