[AMBARI-15235] Display tag for StandBy name node should not be changed to NameNode if there is an active namenode - ASF JIRA

Attach files

Attach Screenshot

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Critical
Resolution: Fixed
Affects Version/s: 2.2.0
Fix Version/s: 2.2.2
Component/s: ambari-web
Labels:
None

Description

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.