[SERVER-15425] Make new replication code resilient to members being removed from the replset config Created: 26/Sep/14 Updated: 25/Oct/14 Resolved: 08/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: | 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: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently the _slaveInfoMap in ReplicationCoordinatorImpl is never cleared out, which can cause an fassert in prepareReplSetUpdatePositionCommand {handshakes}if a node in the map can't be found in the config. Simplest way to deal with this seems to be to remove entries from the map on reconfig if the memberID can no longer be found in the new config |
| Comments |
| Comment by Githook User [ 08/Oct/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Spencer Brody (Inactive) [ 26/Sep/14 ] |
|
Example of this in the wild: http://buildlogs.mongodb.org/MCI_windows-64-2k8/builds/93383/test/sharding_0/mongos_no_replica_set_refresh.js |