[DOCS-7123] Report readConcernMajorityOpTime in ReplSetGetStatus Created: 09/Feb/16  Updated: 11/Jan/17  Resolved: 07/Dec/16

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: groom
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-22445 Report readConcernMajorityOpTime in r... Closed
Participants:
Days since reply: 8 years, 1 week, 1 day ago

 Description   

SERVER-22445 adds readConcernMajorityOpTime to ReplSetGetStatus. This OpTime is only displayed when readConcern: Majority is enabled. This ticket makes a new subsection, OpTimes, in the non-member section of ReplSetGetStatus. This refers to the OpTime used for readConcern: Majority calls, (the committed snapshot OpTime) that exists on the reporting node.

As an example:

{
	"set" : "repl",
	"date" : ISODate("2016-02-09T15:59:14.296Z"),
	"myState" : 1,
	"term" : NumberLong(23),
	"heartbeatIntervalMillis" : NumberLong(2000),
	"OpTimes" : {
		"lastCommittedOpTime" : {
			"ts" : Timestamp(1455033548, 1),
			"t" : NumberLong(23)
		},
		"readConcernMajorityOpTime" : {
			"ts" : Timestamp(1455033548, 1),
			"t" : NumberLong(23)
		}
	},
	"members" : [
		{
			"_id" : 0,
			"name" : "eshamaharishi-X9DAi:33000",
			"health" : 1,
			"state" : 1,
			"stateStr" : "PRIMARY",
			"uptime" : 7,
			"optime" : {
				"ts" : Timestamp(1455033548, 1),
				"t" : NumberLong(23)
			},
			"optimeDate" : ISODate("2016-02-09T15:59:08Z"),
			"infoMessage" : "could not find member to sync from",
			"electionTime" : Timestamp(1455033547, 1),
			"electionDate" : ISODate("2016-02-09T15:59:07Z"),
			"configVersion" : 1,
			"self" : true
		}
	],
	"ok" : 1
}


Generated at Thu Feb 08 07:53:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.