ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-15953) NameNode Last Checkpoint script alert definition does not trigger based on uncommitted transactions
Date Mon, 18 Apr 2016 22:58:25 GMT

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

Siddharth Wagle updated AMBARI-15953:
-------------------------------------
    Summary: NameNode Last Checkpoint script alert definition does not trigger based on uncommitted
transactions  (was: NameNode Last Checkpoint script alert definition does not default threshold
to trigger based on uncommitted transactions)

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