[SERVER-20189] changing replica node follower mode under protocol version 1 while standing for election crashes Created: 28/Aug/15  Updated: 25/Jan/17  Resolved: 10/Sep/15

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

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: RPL 9 (09/18/15)
Participants:

 Description   

The crash is due to an invariant in ReplicationCoordinatorImpl::_setFollowerModeFinish that is applicable to protocol version 0 only.



 Comments   
Comment by Githook User [ 08/Sep/15 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-20189 fixed setFollowerMode to not expect valid freshness checker under protocol version 1
Branch: master
https://github.com/mongodb/mongo/commit/5c6c4dec8362f412b2bb34421e58d8af757a2318

Comment by Githook User [ 08/Sep/15 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-20189 added non-blocking version of ReplicationCoordinatorImpl::setFollowerMode
Branch: master
https://github.com/mongodb/mongo/commit/b52f41433e71838e29f4c877be96f2d298d734b3

Comment by Githook User [ 08/Sep/15 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-20189 ReplCoordTest now owns the replication executor
Branch: master
https://github.com/mongodb/mongo/commit/1925a134af14aec6b8a5d61f2f1c5d122c703aa6

Comment by Eric Milkie [ 01/Sep/15 ]

This is actually rolling back because there is only one op in the oplog and it is the n-op from the election.

Generated at Thu Feb 08 03:53:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.