[DOCS-5671] Basic deployment cannot tolerate loss of a replica Created: 18/Jun/15  Updated: 11/Jan/17  Resolved: 18/Jun/15

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

Type: Improvement Priority: Major - P3
Reporter: Andre Spiegel Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates DOCS-5670 Loss of 1 node in Ops Manager can ren... Closed
Related
is related to DOCS-5670 Loss of 1 node in Ops Manager can ren... 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.
Ops Manager needs to provide a better error message (actually, right now it doesn't report any error in the UI at all) when this situation occurs and users cannot even log in.

And if two members of a full three-member replica set were lost, there would still have to be a conclusive error message so users can understand why Ops Manager is no longer functional.

Thanks for considering this.


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