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

Hadoop QA commented on AMBARI-14898:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12786018/AMBARI-14898.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5177//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5177//console

This message is automatically generated.

> Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari 
> Web UI
> ------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14898
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14898
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-14898.patch
>
>
> Script alerts, such as *Ambari Agent / Host Disk Usage* needs to have some 
> metrics Externalized. 
> The Usage screens relies on the alert_disk_space.py script to collect metrics 
> such as Disk utilization (percentage) and directory being checked. 
> The problem is that the directories being check in this script are: 
> 1. ROOT ("/") 
> 2. /usr/hdp 
> If ROOT is OK, then "/usr/hdp" is checked subsequently. However if ROOT is 
> NOT OK (>80% utilization) then "/usr/hdp" is ignored and the "CRITICAL" tag 
> applies to ROOT. 
> This would work on a OOTB standard cluster. However, many users, have 
> Partitions for the hadoop directories. In this instance, "/" is static, no 
> new content will be added. In this instance being at 80 or 90% is OK, this 
> directory will never grow beyond that. 
> "/usr/hdp" is a separate partition that grows in time. 
> Based on the above described check, the 80% of the root partition will 
> trigger a "CRITICAL" message, although the "/usr/hdp" partition is OK. 
> The selection of what directory is being checked should be EXTERNALIZED to a 
> configurable property to avoid these kinds of misleading messages. 
> CONVERSELY --- what constitutes "OK" "WARN" or "CRIT" (the percentage that 
> triggers these) should be left up to the user, not hardcoded in the script. 
> This is a request to externalize the directories that should be checked, as 
> well as the Percentages into an external configurable property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to