[SERVER-17302] consider blacklist in shouldChangeSyncSource Created: 17/Feb/15 Updated: 19/Sep/15 Resolved: 20/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.1, 3.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Matt Dannenberg |
| 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 |
| Backport Completed: | |
| Sprint: | RPL 0 3/13/15 |
| Participants: |
| Description |
|
Currently, shouldChangeSyncSource() does not consider _memberIsBlackListed(). This could cause excessive network traffic and slowness on a replica set secondary, if a blacklisted sync source is more than 30 seconds ahead of the current sync source for such secondary node. |
| Comments |
| Comment by Githook User [ 03/Mar/15 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: (cherry picked from commit 49fe3ce86ea1d9ac416de932b7d6a6f17248e27b) |
| Comment by Githook User [ 20/Feb/15 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |