[DOCS-2330] Our distributed replicaset recommendation in docs don't match w/ support Created: 02/Dec/13  Updated: 30/Oct/23  Resolved: 07/Apr/16

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

Type: Improvement Priority: Major - P3
Reporter: Nicholas Tang Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by DOCS-2477 Update replication / election docs to... Closed
is duplicated by DOCS-2687 Replica/Sharding Docs with 3 DataCenters Closed
Related
related to DOCS-4011 Need a tutorial on setting up a DR site. Closed
Participants:
Days since reply: 7 years, 44 weeks, 6 days ago

 Description   

When a user asks about setting up geographically diverse replicasets, we recommend using an odd number of data centers so that they can keep a majority live even after one fails. Obviously, for some customers that's not an option, but for 99% of them, sticking an arbiter up in the cloud is actually feasible and is the best answer to their problems.

Our docs, however, recommend putting a majority of nodes in a single location, thereby guaranteeing that if that location goes offline, that their replicaset will be read-only (or if it's a sharded environment, completely unusable). Mentioning that as an option for users who absolutely, positively can't have a 3rd location is fine, but it shouldn't be the default recommendation.

Doc is here:
http://docs.mongodb.org/manual/tutorial/deploy-geographically-distributed-replica-set/

Thanks,
Nicholas



 Comments   
Comment by Githook User [ 07/Apr/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-2330 tweaks to distributed replica set
Branch: v2.4
https://github.com/mongodb/docs/commit/cd25d7436e08252501b16aaf1d434f5ddc74c838

Comment by Githook User [ 07/Apr/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-2330 tweaks to distributed repl set
Branch: v2.6
https://github.com/mongodb/docs/commit/f47a9aab69b9469a0f4e8914a189694f1dd2ab8d

Comment by Githook User [ 07/Apr/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-2330 tweaks to distributed repl set
Branch: v3.0
https://github.com/mongodb/docs/commit/8cbb1ff97c10e08db4e75cfe1788c9f91ab656ed

Comment by Githook User [ 07/Apr/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-2330 tweaks to distributed repl set
Branch: master
https://github.com/mongodb/docs/commit/09c6180ed8249bfd757969459165fc7c5b582af6

Comment by Githook User [ 07/Apr/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-2330 distribute replica set
Branch: v2.2
https://github.com/mongodb/docs/commit/29c16ae0b0b74fed4478dc00449ce362c2f246f5

Comment by Githook User [ 07/Apr/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-2330 distribute replica set
Branch: v2.4
https://github.com/mongodb/docs/commit/4a340c5d7f916591c8647d53709b070d9340fd18

Comment by Githook User [ 07/Apr/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-2330 distribute replica set
Branch: v2.6
https://github.com/mongodb/docs/commit/a30622fbcccbfed011a622b8614f39ab528435b2

Comment by Githook User [ 07/Apr/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-2330 distribute replica set
Branch: v3.0
https://github.com/mongodb/docs/commit/0137207b9a55cddf05ae9aa5bd5085d05fefac77

Comment by Githook User [ 06/Apr/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-2330 distribute replica set
Branch: master
https://github.com/mongodb/docs/commit/60eecf96bbf1395e6e8b54a37b91cfdfba6c9fde

Comment by Alexander Marquardt [ 09/Mar/16 ]

The above recommendations are not totally consistent with our Whitepaper https://www.mongodb.com/collateral/mongodb-multi-data-center-deployments, which gives an example with three data centres that have a 2-2-1 configuration.

Comment by Damien Gasparina [ 09/Mar/16 ]

You can find the same kind of recommendation on:

I think it would be best to recommend by default to avoid keeping a majority in one location. This to spare a single point of failure and to allow automatic failover instead of manual failover in case of a DC/general issue.

Cheers,
Damien

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