[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: |
|
||||
| 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: |
| 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: |