[SERVER-8858] Extend `isMaster` to return opTime and writeDate Created: 05/Mar/13  Updated: 26/Sep/17  Resolved: 02/May/16

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

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

Issue Links:
Related
related to DOCS-7787 isMaster lastWrite field Closed
related to SERVER-23892 Do periodic replicated writes every 1... Closed
is related to SERVER-23893 Increment maxWireVersion for maxStale... Closed
is related to SERVER-4936 Server support for "maxStalenessMS" r... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 14 (05/13/16)
Participants:
Case:

 Description   

Required to support new read preference option maxStalenessMS.



 Comments   
Comment by A. Jesse Jiryu Davis [ 11/Jul/16 ]

Note to driver authors: the isMaster response now includes this:

> db.isMaster()
{
        "ok": 1,
        // ... other fields ...
	"lastWrite" : {
		"opTime" : {
			"ts" : Timestamp(1468278140, 2),
			"t" : NumberLong(1)
		},
		"lastWriteDate" : ISODate("2016-07-11T23:02:20Z")
	}
}

Comment by Githook User [ 02/May/16 ]

Author:

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

Message: SERVER-8858 add optime and optimeDate to isMaster response
Branch: master
https://github.com/mongodb/mongo/commit/ef7e7261f934d2b29c9a1cbf7731a4f733e91627

Comment by Eliot Horowitz (Inactive) [ 05/Mar/13 ]

This is not something the drivers should be doing in this manner.

The 2 ideas we may do are: SERVER-3346 or SERVER-4936

Generated at Thu Feb 08 03:18:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.