ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <>
Subject [jira] [Updated] (AMBARI-17339) Ambari alert "NameNode Last Checkpoint" failing when NameNode is HA
Date Tue, 21 Jun 2016 15:18:58 GMT


Andrew Onischuk updated AMBARI-17339:
    Status: Patch Available  (was: Open)

> Ambari alert "NameNode Last Checkpoint" failing when NameNode is HA
> -------------------------------------------------------------------
>                 Key: AMBARI-17339
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.4.0
>         Attachments: AMBARI-17339.patch, 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

View raw message