[DOCS-7787] isMaster lastWrite field Created: 02/May/16  Updated: 13/Dec/16  Resolved: 06/Dec/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 3.4.0

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Andrew Aldridge
Resolution: Done Votes: 0
Labels: docs-3.4
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-8858 Extend `isMaster` to return opTime an... Closed
Participants:
Days since reply: 7 years, 9 weeks, 1 day ago
Story Points: 0.5

 Description   

When run on a replicaset, the isMaster command now returns a new top level field called "lastWrite". lastWrite contains the "opTime" and "lastWriteDate" which is the optime and date of the last applied write on that server. If --enableMajorityReadConcern is specified, "majorityOpTime" and "majorityWriteDate" will also appear. They return the optime and date of the last committed snapshot, which is the latest optime and date of the writes that would be returned if a readConcern majority read were issued against that server.

"lastWrite" : {
		"opTime" : {
			"ts" : Timestamp(1462197355, 1),
			"t" : NumberLong(1)
		},
		"lastWriteDate" : ISODate("2016-05-02T13:55:55Z"),
		"majorityOpTime" : {
			"ts" : Timestamp(1462197355, 1),
			"t" : NumberLong(1)
		},
		"majorityWriteDate" : ISODate("2016-05-02T13:55:55Z")
	},



 Comments   
Comment by Githook User [ 13/Dec/16 ]

Author:

{u'username': u'i80and', u'name': u'Andrew Aldridge', u'email': u'i80and@foxquill.com'}

Message: DOCS-7787: Document isMaster.lastWrite

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/4811e84cc33eed77695374ad24e22fd456f81248

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