You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Bourne (JIRA)" <ji...@apache.org> on 2013/10/21 03:25:46 UTC
[jira] [Updated] (AMBARI-3545) After nn perform failover, HDFS is
OK, but Ambari web show HDFS can`t service
[ https://issues.apache.org/jira/browse/AMBARI-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bourne updated AMBARI-3545:
---------------------------
Description:
After nn perform failover, HDFS is OK, but Ambari web show HDFS can`t service, because nn can not connect, and Nagios alert.
1.stop active namenode
2.standby namenode become active(see from namenode UI)
3.but ambari web page shows namenode fall down
was:After nn perform failover, HDFS is OK, but Ambari web show HDFS can`t service, because nn can not connect, and Nagios alert.
> After nn perform failover, HDFS is OK, but Ambari web show HDFS can`t service
> -----------------------------------------------------------------------------
>
> Key: AMBARI-3545
> URL: https://issues.apache.org/jira/browse/AMBARI-3545
> Project: Ambari
> Issue Type: Bug
> Components: site
> Affects Versions: 1.4.1
> Reporter: Bourne
>
> After nn perform failover, HDFS is OK, but Ambari web show HDFS can`t service, because nn can not connect, and Nagios alert.
> 1.stop active namenode
> 2.standby namenode become active(see from namenode UI)
> 3.but ambari web page shows namenode fall down
--
This message was sent by Atlassian JIRA
(v6.1#6144)