[DOCS-2477] Update replication / election docs to provide better clarity about vote manipulation Created: 06/Jan/14 Updated: 04/Mar/15 Resolved: 17/Oct/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | mongodb-2.6 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nicholas Tang | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 10 years, 6 weeks, 2 days ago | ||||||||||||
| Description |
|
We could use some clarification in our docs regarding elections, and various high availability schemes, with some stronger recommendations regarding vote manipulation (when to do it, when not to, and the fact that you really should only set nodes to 0 or 1 vote, ideally). True high availability across 2 locations is really only possible w/ at least 3 locations (i.e. a third to host the tie-breaker - a solo arbiter on AWS can fit this bill nicely), and no amount of vote manipulation will successfully solve that problem w/ the current scheme. |