[SERVER-15160] TopologyCoordinatorImpl should not always step down on reconfig Created: 05/Sep/14 Updated: 10/May/17 Resolved: 10/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
The heartbeating implementation in TopologyCoordinatorImpl does not attempt to stay primary across reconfigs where new elections could be avoided. It should, to be consistent with old behavior and to minimize the number of unnecessary elections. |
| Comments |
| Comment by Andy Schwerin [ 24/Jul/15 ] |
|
moboyle, if you have a specific example of what you believe to be a failure, could you file a new ticket? |
| Comment by Michael O'Boyle [ 23/Jul/15 ] |
|
It doesn't look like the dependent (duplicate) tasks were truly fixed with this fix. |
| Comment by Githook User [ 14/Oct/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 14/Oct/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 14/Oct/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 10/Oct/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |