Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 18 Apr 2016 22:53:25 +0000 (UTC)
From: "Siddharth Wagle (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12959812.1461019973000.261463.1461020005425@Atlassian.JIRA>
In-Reply-To: <JIRA.12959812.1461019973000@Atlassian.JIRA>
References: <JIRA.12959812.1461019973000@Atlassian.JIRA>
 <JIRA.12959812.1461019973825@arcas>
Subject: [jira] [Created] (AMBARI-15953) NameNode Last Checkpoint script
 alert definition does not default threshold to trigger based on uncommitted
 transactions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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)