You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Rahul Pathak (JIRA)" <ji...@apache.org> on 2016/06/08 11:00:26 UTC

[jira] [Updated] (AMBARI-17107) Ambari Alert for NameNode Last Checkpoint in HA

     [ https://issues.apache.org/jira/browse/AMBARI-17107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rahul Pathak updated AMBARI-17107:
----------------------------------
    Summary: Ambari Alert for NameNode Last Checkpoint in HA  (was: Ambari Alert for HDFS Last Checkpoint in HA)

> Ambari Alert for NameNode Last Checkpoint in HA
> -----------------------------------------------
>
>                 Key: AMBARI-17107
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17107
>             Project: Ambari
>          Issue Type: Bug
>          Components: alerts
>    Affects Versions: 2.2.2
>         Environment: Hortonworks hadoop HDP 2.4.2 with HDFS HA enabled.
>            Reporter: Rahul Pathak
>              Labels: easyfix
>
> As can been seen in https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py
> At line 
> {code}NN_HTTP_ADDRESS_KEY = '{{hdfs-site/dfs.namenode.http-address}}'{code}
> It will not work in case of HA enabled cluster. 
> In case of HA this property will not exist and alert will fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)