-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Cloud Manager
-
Labels:
-
Environment:
*Location*: https://docs.opsmanager.mongodb.com//current/core/deployments/#basic-deployment
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36
*Referrer*: https://jira.mongodb.org/browse/HELP-994
*Screen Resolution*: 1440 x 900
*repo*: REPONAME
*source*: core/deployments
*Location*: https://docs.opsmanager.mongodb.com//current/core/deployments/#basic-deployment *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36 *Referrer*: https://jira.mongodb.org/browse/HELP-994 *Screen Resolution*: 1440 x 900 *repo*: REPONAME *source*: core/deployments
Add note under "Basic Deployment" on https://docs.opsmanager.mongodb.com//current/core/deployments/
saying "The basic deployment provides durability in case of failure (via a redundant copy of the data) but not high availability. The [Advanced Deployment] described below is highly available; it can continue to accept writes even with temporary loss of a database node."
AND on https://docs.opsmanager.mongodb.com//current/tutorial/install-basic-deployment/
add "The basic deployment provides durability in case of failure (via a redundant copy of the data) but not high availability. The [Advanced Deployment' described on the Ops Manager Example Deployments page] is highly available; it can continue to accept writes even with temporary loss of a database node."