You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2016/04/19 00:53:25 UTC

[jira] [Created] (AMBARI-15953) NameNode Last Checkpoint script alert definition does not default threshold to trigger based on uncommitted transactions

Siddharth Wagle created AMBARI-15953:
----------------------------------------

             Summary: NameNode Last Checkpoint script alert definition does not default threshold to 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)