[SERVER-12872] Be able to guarantee who a node will use as a target for initial sync Created: 24/Feb/14 Updated: 02/Nov/17 Resolved: 17/Jun/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.9 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Osmar Olivo | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently, we can use the rs.syncFrom() helper to provide a temporary override on who we want a node to sync-off of. However, when performing an initial sync, either because of falling off the oplog or adding a node, we have no mechanism to do this. The second we start up the server it will begin initial sync without a way for us who to determine whom we want to sync off of (without downtime). Potentially putting unwanted load on a primary or other node. It would be nice to make syncFrom somehow determinable at startup time prior to the initial sync beginning. |
| Comments |
| Comment by Eric Milkie [ 17/Jun/14 ] |
|
Discussion consolidated in |
| Comment by James Blackburn [ 27/Mar/14 ] |
|
This is quite an important feature. We find that rebuild read load is sufficient to kill nodes on RHEL5. |