[SERVER-2297] when adding a replica, especially a delayed replica allow for throttling of initial replication to avoid spikes Created: 28/Dec/10 Updated: 17/Mar/11 Resolved: 28/Dec/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kenny Gorman | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
When adding a delayed standby we saw response times go from ~2ms to ~20ms during the period the data was being replicated. We plan on having the dataset grow to a much larger level and thus the spike duration would be longer. We would like a feature that allows throttling of initial replication so the spike is smaller but perhaps longer. This must be weighed against never being able to catch up if it's throttled too far. |
| Comments |
| Comment by Kenny Gorman [ 28/Dec/10 ] |
|
Agreed http://jira.mongodb.org/browse/SERVER-1829 is a good approach. |
| Comment by Eliot Horowitz (Inactive) [ 28/Dec/10 ] |
|
Also, look at |
| Comment by Kenny Gorman [ 28/Dec/10 ] |
|
Actually, I think --fastsync meets our needs. We will test and decide. |