[DOCS-2850] 4 member replica set is confusing Created: 04/Mar/14 Updated: 16/Mar/15 Resolved: 02/Jul/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.8 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Sherry Ger | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 33 weeks ago |
| Description |
|
Here is the link of the document in question The document uses a four member replica set example. This can be misleading to users who are new to MongoDB. They may think it is OK to have a four nodes replica set; all they have to do is to adjust the node priority. Please make it a five member example instead of four or specify that there is an arbiter in addition to the 4 members. |
| Comments |
| Comment by Kay Kim (Inactive) [ 02/Jul/14 ] |
|
Was done as part of this commit (we specify a sample replica set of 3 members and update conf of only one member – the one we're setting priority to 0) |