NameNode Last Checkpoint alert for Namenode HA cluster

[#1]

NameNode Last Checkpoint alert of Ambari looks to have bug in case cluster have Namenode HA configured.

The alert runs script /var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py

This script uses dfs.namenode.http-address property of hdfs-site.xml as per below

NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'

However in case of HA enabled cluster this will not work as this property will not be there in HA enabled cluster.

Can anyone confirm if this is a bug?

Rahul

[#2 · Accepted solution]

This was confirmed as bug and fixed in Ambari 2.4

https://issues.apache.org/jira/browse/AMBARI-17339

[#3]

Hi @Rahul Pathak

Can you please add the bug ticket and patch link?

Regards,

Wendell

[#4]

https://issues.apache.org/jira/browse/AMBARI-17339