[DOCS-9146] Comment on: "manual/core/replica-set-architectures.txt" Created: 14/Oct/16  Updated: 18/Oct/16  Resolved: 18/Oct/16

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Joe Drumgoole (Inactive) Assignee: Allison Reinheimer Moore
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.mongodb.com/manual/core/replica-set-architectures/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
Referrer: https://docs.mongodb.com/manual/core/replica-set-sync/
Screen Resolution: 1920 x 1080


Participants:
Days since reply: 7 years, 17 weeks, 1 day ago
Story Points: 0.25

 Description   

On this page you recommend three member replica sets.

However earlier on you recommend:

The minimum recommended configuration for a replica set is: A primary, a secondary, and an arbiter. Most deployments, however, will keep three members that store data: A primary and two secondary members.

See https://docs.mongodb.com/manual/core/replica-set-architectures/ for the earlier recommendation.



 Comments   
Comment by Githook User [ 18/Oct/16 ]

Author:

{u'username': u'schmalliso', u'name': u'Allison Moore', u'email': u'allison.moore@10gen.com'}

Message: DOCS-9146: rephrases rs deployment topology recommendation
Branch: v3.2
https://github.com/mongodb/docs/commit/9b6be9623fddfb449e2c10abdfdb3088642b3f71

Comment by Githook User [ 18/Oct/16 ]

Author:

{u'username': u'schmalliso', u'name': u'Allison Moore', u'email': u'allison.moore@10gen.com'}

Message: DOCS-9146: rephrases rs deployment topology recommendation
Branch: master
https://github.com/mongodb/docs/commit/73dbf286bd504736aeb86ed3de5ac1f56c2718cf

Comment by Joe Drumgoole (Inactive) [ 18/Oct/16 ]

Like it.

Comment by Allison Reinheimer Moore [ 18/Oct/16 ]

joe.drumgoole I've rephrased the paragraph in question to lead with the better option and emphasize that three data-bearing members is the way to go. If you'd like to have a look at the code review, I'd be most obliged!

Here's the link: https://mongodbcr.appspot.com/99750001/

Comment by Joe Drumgoole (Inactive) [ 17/Oct/16 ]

A 2+1 replica set (2 data nodes, on arbiter). A 2+1 arbiter configuration is less safe than a three node config. We need to decide what we recommend, low cost but unsafe or higher cost but keeps the data safe. We are recommending two different things on two different pages but the worst option is the first one customers come across.

Comment by Allison Reinheimer Moore [ 14/Oct/16 ]

joe.drumgoole Thanks for your ticket!

At the bottom of the Replica Set Architectures page, we link to the Three Member Replica Sets page with a caption that reads "Three-member replica sets provide the minimum recommended architecture for a replica set." The 3-member rs page then describes two deployments: two data-bearing members and an arbiter, and three data-bearing members. This is consistent with the sentence you quoted from the Replica Set Members page

As such, I don't think we're being contradictory. However, it's very possible I've missed something, so please let me know if that's the case!

Generated at Thu Feb 08 07:57:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.