[
https://issues.apache.org/jira/browse/AMBARI-17127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321623#comment-15321623
]
Hadoop QA commented on AMBARI-17127:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12808996/AMBARI-17127.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 1 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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7262//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7262//console
This message is automatically generated.
> Ambari Stale Alert Triggers For Server-Side Performance Alert
> -------------------------------------------------------------
>
> Key: AMBARI-17127
> URL: https://issues.apache.org/jira/browse/AMBARI-17127
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.4.0
>
> Attachments: AMBARI-17127.patch, AMBARI-17127.patch
>
>
> If the Ambari Server is restarted after being down for several minutes, the
> "Ambari Server Performance" alert will trigger as being stale. This is
> because the {{StaleAlertRunnable}} is not checking to ensure that Ambari has
> been up and running long enough to have run the alert.
> The {{StaleAlertRunnable}} should verify that the uptime of Ambari is greater
> than staleness interval.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
