[SERVER-22505] update requestVotes to use durable instead of committed to describe its OpTime Created: 08/Feb/16  Updated: 07/Feb/17  Resolved: 10/Feb/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.2.1
Fix Version/s: 3.2.13, 3.3.2

Type: Bug Priority: Major - P3
Reporter: Matt Dannenberg Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.2
Sprint: Repl 10 (02/19/16)
Participants:

 Description   

The committedOpTime is a different concept from the durableOpTime. RequestVotes uses the latter but misleadingly refers to it as the former.



 Comments   
Comment by Githook User [ 06/Feb/17 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-22505 describe RequestVotes OpTime as durable rather than committed

(cherry picked from commit d84483b8a6a9890c2c93f267d8c28969dc563c37)
Branch: v3.2
https://github.com/mongodb/mongo/commit/0175d0e0bf82d67e9a5e651f9b96c374c1eaedef

Comment by Githook User [ 10/Feb/16 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-22505 describe RequestVotes OpTime as durable rather than committed
Branch: master
https://github.com/mongodb/mongo/commit/d84483b8a6a9890c2c93f267d8c28969dc563c37

Comment by Githook User [ 10/Feb/16 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-22505 describe RequestVotes OpTime as durable rather than committed
Branch: renamerequestvotes
https://github.com/mongodb/mongo/commit/d84483b8a6a9890c2c93f267d8c28969dc563c37

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