[SERVER-29809] Multiple Arbiter Created: 23/Jun/17 Updated: 23/Jun/17 Resolved: 23/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | dannywcw | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Newbie here and need advice in implementing mongodb high availability Details: With this setup, AZ2(Arbiter) would be a single point of failure because it doesn't have any backup server. Revise setup: Would the revised setup be feasible? Can Primary & Secondary have multiple entries of arbiter? Or is advisable to have a setup without an arbiter like this (AZ1 (Primary, Secondary), AZ2 (Secondary, Secondary, Secondary) ? |
| Comments |
| Comment by Kelsey Schubert [ 23/Jun/17 ] |
|
Hi dannywcw, Thanks for your report. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. Additionally, this documentation on geographically distributed replica sets may be helpful to review. Kind regards, |