ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15953) NameNode Last Checkpoint script alert definition does not trigger based on uncommitted transactions
Date Wed, 20 Apr 2016 03:36:25 GMT

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

Hudson commented on AMBARI-15953:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #4691 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4691/])
AMBARI-15953. NameNode Last Checkpoint script alert definition does not (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0a13257f80dbb6b4b2a7fbef24c8f27e5eeb6278])
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_alert_checkpoint_time.py
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/alerts.json
* ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
* ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_checkpoint_time.py


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

Mime
View raw message