ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17339) Ambari alert "NameNode Last Checkpoint" failing when NameNode is HA
Date Wed, 22 Jun 2016 10:03:58 GMT

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

Andrew Onischuk updated AMBARI-17339:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.4

> Ambari alert "NameNode Last Checkpoint" failing when NameNode is HA
> -------------------------------------------------------------------
>
>                 Key: AMBARI-17339
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17339
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17339.patch
>
>
> The "NameNode Last Checkpoint" alert is implemented in
> _alert_checkpoint_time.py_. This script uses the value of **dfs.namenode.http-
> address** property for querying the last checkpoint timestamp.
> This works fine when the NN is not in HA mode. However when NN is in HA mode
> this property is either not defined or might not be pointing to the right NN
> instance.
> The script needs to be improved such as to figure out if the NN is in HA mode.
> If it's in HA mode do not use **dfs.namenode.http-address** property but
> rather determine the correct URL to connect to similarly as how it's done in
> the _alert_ha_namenode_health.py_



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

Mime
View raw message