You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Kyle R Dunn (JIRA)" <ji...@apache.org> on 2016/03/30 07:05:25 UTC
[jira] [Commented] (ATLAS-600) HA Namenode Health Alert showing
invalid state
[ https://issues.apache.org/jira/browse/ATLAS-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217396#comment-15217396 ]
Kyle R Dunn commented on ATLAS-600:
-----------------------------------
I recently did a deployment via Blueprint with an HA Namenode configuration. Several parameters did not receive host group substitution (yarn.nodemanager.bind-host, Knox topology.xml Namenode references, all hostname references in individual YARN configuration host groups). Also, 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.
> HA Namenode Health Alert showing invalid state
> ----------------------------------------------
>
> Key: ATLAS-600
> URL: https://issues.apache.org/jira/browse/ATLAS-600
> Project: Atlas
> Issue Type: Bug
> Reporter: Kyle R Dunn
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)