incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-2928) Add a Nagios alert to check state of NN HA
Date Wed, 28 Aug 2013 17:02:52 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mahadev konar updated AMBARI-2928:
----------------------------------

    Fix Version/s:     (was: 1.4.0)
                   1.4.1
    
> Add a Nagios alert to check state of NN HA
> ------------------------------------------
>
>                 Key: AMBARI-2928
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2928
>             Project: Ambari
>          Issue Type: Improvement
>          Components: agent
>    Affects Versions: 1.4.0
>            Reporter: Dmitry Sen
>            Assignee: Dmitry Sen
>             Fix For: 1.4.1
>
>         Attachments: AMBARI-2928.patch
>
>
> Add Nagios alert
> Title: "NameNode HA Healthy"
> Check if one NN has tag.HAState = active and second NN has tag.HAState = standby.
> Scenarios:
> 1.
> Active + Standby NN are up 
> OK: NameNode HA healthy true; Active<dev01.hortonworks.com>, Standby<dev02.hortonworks.com>,
Unavailable<>
> 2.
> Two Standby NNs are up
> CRITICAL: No Active NN available; Active<>, Standby<dev01.hortonworks.com:dev02.hortonworks.com>,
Unavailable<>
> 3.
> Two Active NN are up
> CRITICAL: No Active NN available; No failover NN available; Active<dev01.hortonworks.com:dev02.hortonworks.com>,
Standby<>, Unavailable<>
> 4.
> Both NN unavailable
> CRITICAL: No Active NN available; No failover NN available: Active<>, Standby<>,
Unavailable<dev01.hortonworks.com:dev02.hortonworks.com>
> 5.
> Only one NameNode in cluster (no additional/standby NameNode configured)
> CRITICAL: No failover NN available: Active<dev01.hortonworks.com>, Standby<>,
Unavailable<>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message