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

Hadoop QA commented on AMBARI-15720:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12797163/AMBARI-15720.v0.patch
  against trunk revision .

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {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/6238//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6238//console

This message is automatically generated.

> AGGREGATE Alerts Should Not Expose Repeat Tolerance or Tolerance Enabled 
> Settings
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-15720
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15720
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Zhe (Joe) Wang
>            Assignee: Zhe (Joe) Wang
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15720.v0.patch
>
>
> {{AGGREGATE}} type alerts should not expose a {{repeat_tolerance}} or 
> {{repeat_tolerance_enabled}} setting in the web client. This is because of 
> the nature of how {{AGGREGATE}} alerts functions. They respond to {{HARD}} 
> alert events and are therefore simply a summary of the known alerts which 
> have already reached their repeat tolerance levels.
> These types of alerts will not honor a global repeat tolerance value 
> ({{cluster-env/alerts_repeat_tolerance}} nor will they honor changes to alert 
> definitions of source type {{AGGREGATE}}.
> They effectively have a tolerance of 1 always.



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

Reply via email to