[SERVER-28680] Fix naming of lastCommittedOp field in replSetRequestVotes Created: 07/Apr/17 Updated: 18/Feb/20 Resolved: 18/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Xuerui Fa |
| Resolution: | Done | Votes: | 0 |
| Labels: | former-quick-wins, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Minor Change | ||||||||
| Sprint: | Repl 2020-02-10, Repl 2020-02-24 | ||||||||
| Participants: | |||||||||
| Description |
|
replSetRequestVotes has a field named "lastCommittedOp". The VoteRequester calls this variable lastDurableOpTime. The correct behavior is to pass in the last applied OpTime, which we do. We should rename all of this to be lastAppliedOpTime. |
| Comments |
| Comment by Githook User [ 18/Feb/20 ] |
|
Author: {'name': 'Xuerui Fa', 'username': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com'}Message: |
| Comment by Judah Schvimer [ 24/Oct/19 ] |
|
We can do this over 2 releases by adding a new "lastApplied" field and then removing the current confusing field. This will have to be gated by FCV. |