[SERVER-22337] Report lastAppliedAndJournaledOptime in replSetGetStatus Created: 28/Jan/16  Updated: 06/Dec/22  Resolved: 22/Mar/16

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

Type: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-23287 Cleanup replSetGetStatus output/code ... Closed
Related
related to SERVER-22276 implement "j" flag in write concern a... Closed
is related to SERVER-22336 Report committedOptime in replSetGetS... Closed
Assigned Teams:
Replication
Backwards Compatibility: Minor Change
Participants:

 Description   

Now (as of SERVER-22276) that we are keeping track of the both the lastApplied and lastAppliedAndJournaled OpTimes we should expose them for use.

Open question: Are they needed yet, or is this just for reporting/diagnostics?



 Comments   
Comment by Ian Whalen (Inactive) [ 26/Apr/19 ]

Switching "Drivers Changes Needed" from "Maybe" to "Not Needed" since this was closed as something other than Fixed.

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