[SERVER-20262] Replica set nodes can get stuck in a state where they will not step themselves down Created: 02/Sep/15  Updated: 06/Nov/15  Resolved: 02/Sep/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.0.6
Fix Version/s: 3.0.7, 3.1.8

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:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Steps To Reproduce:

A reconfig must come in and kill all heartbeat threads between when the node decides to step itself down and when it acts on that decision.

Sprint: RPL 9 (09/18/15)
Participants:

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

Author:

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

Message: SERVER-20262 reset the _stepDownPending bool after cancelling all heartbeats during a reconfig
Branch: master
https://github.com/mongodb/mongo/commit/5c07a707ef242ee3b62de371b5e7522d84bf4b1d

Comment by Githook User [ 02/Sep/15 ]

Author:

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

Message: SERVER-20262 reset the _stepDownPending bool after cancelling all heartbeats during a reconfig
Branch: v3.0
https://github.com/mongodb/mongo/commit/7151c1adcd53e5a6a365e573b1b05e52d5c910e7

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