incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bourne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-3545) After nn perform failover, HDFS is OK, but Ambari web show HDFS can`t service
Date Mon, 21 Oct 2013 01:25:46 GMT

     [ 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)

Mime
View raw message