[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: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 5 years, 3 weeks, 2 days ago | ||||||||
| Epic Link: | DOCSP-1769 | ||||||||
| Description |
DescriptionFor 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
and replSetGetStatus.members[n].optimeDurable.
Scope of changesImpact to Other DocsMVP (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: |
| Comment by Githook User [ 22/Jan/19 ] |
|
Author: {'email': 'kay.kim@mongodb.com', 'name': 'Kay Kim'}Message: |