[DOCS-643] Documentation or Production Notes style page on throttling connection between nodes Created: 25/Oct/12 Updated: 01/Nov/12 Resolved: 01/Nov/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Andre de Frere | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 11 years, 15 weeks, 6 days ago | ||||
| Description |
|
It seems a fairly reasonable use case for someone to want to minimise load between sync-ing nodes by throttling bandwidth. Mongo does not support this out of the box, but it can be done through external controls (iptables for example). There is a large possibility to get QOS type controls wrong and therefore get a detrimental effect, so specific rules are probably not required. Rather, something to point people in the right direction when they have this need would be useful. |
| Comments |
| Comment by Ed Costello [ 01/Nov/12 ] |
|
Knocking severity down until we have some sort of consensus on material like this. |
| Comment by Scott Hernandez (Inactive) [ 26/Oct/12 ] |
|
We should not include docs like this at all as it is more trouble than it is worth. We should address the underlying issue with controlling where replication occurs – which we have in 2.2 and above. |
| Comment by Scott Hernandez (Inactive) [ 25/Oct/12 ] |
|
We should not provide script nor documentation for another program like this. If people want to do this they can read the docs and tutorials online. |