Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
None
-
Fully Compatible
-
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
- is depended on by
-
SERVER-19867 Do not read directly from collections in ReplSetTest to get replication optime
-
- Closed
-
- is documented by
-
DOCS-7123 Report readConcernMajorityOpTime in ReplSetGetStatus
-
- Closed
-