Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.3.2
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 10 (02/19/16), Repl F (01/29/16)
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

Currently we report the optime of each node in the replicaset but we don't report the committedOptime. This can be put at the top of the reporting information.

is depended on by

SERVER-19867 Do not read directly from collections in ReplSetTest to get replication optime

Closed

related to

SERVER-22337 Report lastAppliedAndJournaledOptime in replSetGetStatus

Closed

Assignee:: Judah Schvimer
Reporter:: Judah Schvimer
Participants:: Eric Milkie, Githook User, Judah Schvimer
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jan 28 2016 04:49:36 PM UTC
Updated:: May 03 2017 08:41:52 PM UTC
Resolved:: Feb 02 2016 03:12:34 PM UTC
Confidence Status Last Update:: 28/Jan/16 6:06 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates