[
https://issues.apache.org/jira/browse/AMBARI-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370744#comment-15370744
]
Eric Periard commented on AMBARI-15235:
---------------------------------------
I've been running ambari 2.2.2.0 for two weeks now, whenever nn fails snn kicks
in as active and nn becomes standby.
Ambari still reports both NN's as Active even though the back is fine when
checking with HAadmin command....
> Display tag for StandBy name node should not be changed to NameNode if there
> is an active namenode
> --------------------------------------------------------------------------------------------------
>
> Key: AMBARI-15235
> URL: https://issues.apache.org/jira/browse/AMBARI-15235
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.2.0
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15235.patch
>
>
> On a large cluster with heavy load on NameNode, sometimes there happens to be
> greater latency for Standby NameNode in responding back its JMX metrics which
> results in timeout for the JMX call dome by ambari-server and no JMX data for
> standby NameNode is received sometimes.
> Thus Standby NameNode in such environment responses sometimes by declaring
> itself standby and sometimes doesn't respond quick enough before timeout
> happens.
> Due to this behavior ambari-web keeps alternating frequently between “standby
> namenode” and “namenode”, even though there is no failover.
> As a fix ambari if detects any one namenode to be active should consider
> other to be standby even though JMX call to standby namenode has timedout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
