[SERVER-22336] Report committedOptime in replSetGetStatus Created: 28/Jan/16 Updated: 03/May/17 Resolved: 02/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Sharding 10 (02/19/16), Repl F (01/29/16) | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Judah Schvimer [ 02/Feb/16 ] |
|
ReplSetGetStatus now includes a field "lastCommittedOpTime" that includes the OpTime of the last committed operation of the replicaset. This OpTime could be for an operation not yet replicated to the node reporting it. |
| Comment by Githook User [ 02/Feb/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |
| Comment by Judah Schvimer [ 29/Jan/16 ] |
|
I actually don't think they would need to now that I've looked into it more. I'll change the description. |
| Comment by Eric Milkie [ 29/Jan/16 ] |
|
Why would nodes be keeping track of the committedOpTime for every node? |