[ 
https://issues.apache.org/jira/browse/AMBARI-17339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342271#comment-15342271
 ] 

Hadoop QA commented on AMBARI-17339:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12812206/AMBARI-17339.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7451//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7451//console

This message is automatically generated.

> 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)

Reply via email to