ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kyle R Dunn (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-15624) HA Namenode Health Alert showing invalid state
Date Wed, 30 Mar 2016 05:49:25 GMT
Kyle R Dunn created AMBARI-15624:
------------------------------------

             Summary: HA Namenode Health Alert showing invalid state
                 Key: AMBARI-15624
                 URL: https://issues.apache.org/jira/browse/AMBARI-15624
             Project: Ambari
          Issue Type: Bug
          Components: alerts
    Affects Versions: 2.2.1
            Reporter: Kyle R Dunn


I recently did a deployment via Blueprint with an HA Namenode configuration. Several parameters
did not receive host group substitution requiring the Namenode and Standby namenodes had to
be manually formatted/bootstrapped respectively. Now Ambari alerts shows the stanby namenode
in "unknown" state. If I failover from nn2 to nn1 one Namenode shows in Standby and the other
in unknown. I've restarted Ambari server, HDFS, disabled and reenabled the alert and yet it
persists. hdfs haadmin -getServiceState for nn1 and nn2 show one active and one standby namenode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message