[DOCS-12368] Update replSetGetStatus.optimes to reflect that appliedOpTime & durableOpTime are timestamps in pv0. Created: 16/Jan/19  Updated: 30/Oct/23  Resolved: 22/Jan/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Suganthi Mani Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-12253 Add a comment in "Modify Replica Set ... Closed
Participants:
Days since reply: 5 years, 3 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Description

For MongoDB versions < 4.0 supporting pv0, add a note in replSetGetStatus.optimes stating that "For pv0, replSetGetStatus.optimes.appliedOpTime and replSetGetStatus.optimes.durableOpTime returns the timestamp of the operation" similar to the one mentioned for replSetGetStatus.members[n].optime 

If using protocolVersion: 0optime returns the Timestamp of the last operation applied to this member of the replica set from the oplog." 

and replSetGetStatus.members[n].optimeDurable. 

If using protocolVersion: 0, optime returns the Timestamp of the operation.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 22/Jan/19 ]

Author:

{'email': 'kay.kim@mongodb.com', 'name': 'Kay Kim'}

Message: DOCS-12368: clarify optimes
Branch: v3.4
https://github.com/mongodb/docs/commit/69f5fc2eaf7df935476803f4ec0d5ede101a8778

Comment by Githook User [ 22/Jan/19 ]

Author:

{'email': 'kay.kim@mongodb.com', 'name': 'Kay Kim'}

Message: DOCS-12368: clarify optimes
Branch: v3.6
https://github.com/mongodb/docs/commit/fdccc38566ec71bb4abf92af652da22bb089cae6

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