[DOCS-4108] Clarify "Number of Healthy Members is below" alert Created: 30/Sep/14  Updated: 16/Mar/15  Resolved: 03/Oct/14

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: v1.3.12

Type: Task Priority: Minor - P4
Reporter: James O'Leary Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 9 years, 19 weeks, 5 days ago

 Description   

The section reads as follows :

Number of Healthy Members is below
Sends an alert when a replica set has fewer than the specified number of healthy members. If the replica set has the specified number of healthy members or more, MMS triggers no alert.

A replica set member is healthy if its state, as reported in the rs.status() output, is either PRIMARY or SECONDARY. Hidden secondaries are not counted.

As an example, if you have a replica set with one member in the PRIMARY state, two members in the SECONDARY state, one hidden member in the SECONDARY, one ARBITER, and one member in the RECOVERING state, then the healthy count is 3.

The example does infer that arbiters are not counted but please change the middle paragraph to read :

A replica set member is healthy if its state, as reported in the rs.status() output, is either PRIMARY or SECONDARY. Hidden secondaries and ARBITERS are not counted.



 Comments   
Comment by Githook User [ 03/Oct/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-4108: clarification with regards to arbiters
Branch: v1.5
https://github.com/10gen/mms-docs/commit/74b18cc273140d0e201b162c8b1dcd24847b1860

Comment by Githook User [ 03/Oct/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-4108: clarification with regards to arbiters
Branch: master
https://github.com/10gen/mms-docs/commit/a70efd69bf640792f1b40205bbb88bb595ecb2aa

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