[SERVER-22466] How to access node of a replica set when 6 out of 7 nodes crashes Created: 04/Feb/16 Updated: 04/Feb/16 Resolved: 04/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Wei-Chih Ting | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
We have 2 IDC each with 2 nodes and 1 arbiter and a 3rd IDC with 1 node with very low priority. |
| Comments |
| Comment by Ramon Fernandez Marina [ 04/Feb/16 ] |
|
wcting@loftechs.com, please take a look at the documentation for high availability for replica sets as well as the replica set tutorials. You'll either need more nodes or a different topology for the scenario you describe. Please note that the 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, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources. Regards, |