[DOCS-5670] Loss of 1 node in Ops Manager can render it unusable Created: 18/Jun/15  Updated: 11/Jan/17  Resolved: 07/Jan/16

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: Rachelle Palmer Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by DOCS-5671 Basic deployment cannot tolerate loss... Closed
Related
related to DOCS-5671 Basic deployment cannot tolerate loss... Closed
Participants:
Days since reply: 8 years, 34 weeks, 6 days ago

 Description   

The "Basic Deployment", as described in the documentation, uses a 2+1 member replica set as the application database. As all writes to this database seem to use w=2, loss of one of the data bearing nodes means that Ops Manager is no longer operational. Users cannot log in, and no monitoring data can be ingested.

Our documentation does explain that (https://docs.opsmanager.mongodb.com/v1.6/core/deployments/#basic-deployment), but the hint needs to be a lot more prominent.


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