[SERVER-27889] Change catchup.js to be resilient to replSetStepUp failing because the node is already a candidate Created: 01/Feb/17  Updated: 05/Apr/17  Resolved: 02/Feb/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.4.3, 3.5.3

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: Repl 2017-02-13
Participants:
Linked BF Score: 0

 Description   

Catchup.js disconnects and then reconnects the primary and a secondary. Then later on it tries to step up a secondary. This stepUp can fail if the secondary stepping up is the same one that was temporarily disconnected from the primary and it had tried to run for election during that time.



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

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-27889 Handle case in catchup.js where stepUp fails due to node already being a candidate.

(cherry picked from commit 81901db84f0245dcf616e638366def74e4169c69)
Branch: v3.4
https://github.com/mongodb/mongo/commit/c2a66a38b2b8e9573f0f334934ac417dadf33ca8

Comment by Githook User [ 02/Feb/17 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-27889 Handle case in catchup.js where stepUp fails due to node already being a candidate.
Branch: master
https://github.com/mongodb/mongo/commit/81901db84f0245dcf616e638366def74e4169c69

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