[SERVER-16455] prohibit simultaneous heartbeat reconfig and candidacy role state Created: 25/Nov/14 Updated: 18/Dec/14 Resolved: 11/Dec/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | Eric Milkie |
| 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 |
| Participants: |
| Description |
|
It is possible that immediately before heartbeatReconfigFinish, we could transition to role Candidate. We cannot finish a reconfig while in role state Candidate. To fix this, we shall immediately call processLoseElection() if we detect that we have transitioned to role Candidate while the config state is kConfigHBReconfiguring, which will clear the Candidate role state. Original description: |
| Comments |
| Comment by Githook User [ 11/Dec/14 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |