[
https://issues.apache.org/jira/browse/AMBARI-15953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247075#comment-15247075
]
Hadoop QA commented on AMBARI-15953:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12799401/AMBARI-15953.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6524//console
This message is automatically generated.
> NameNode Last Checkpoint script alert definition does not trigger based on
> uncommitted transactions
> ---------------------------------------------------------------------------------------------------
>
> Key: AMBARI-15953
> URL: https://issues.apache.org/jira/browse/AMBARI-15953
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 2.4.0
>
> Attachments: AMBARI-15953.patch
>
>
> The 'NameNode Last Checkpoint' alert description says "This service-level
> alert will trigger if the last time that the NameNode performed a checkpoint
> was too long ago. It will also trigger if the number of uncommitted
> transactions is beyond a certain threshold."
> But the default alert definition seems to miss the threshold parameters for
> alerting the number of uncommitted transactions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
