[
https://issues.apache.org/jira/browse/AMBARI-17127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323171#comment-15323171
]
Hudson commented on AMBARI-17127:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5044 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5044/])
AMBARI-17127 - Ambari Stale Alert Triggers For Server-Side Performance
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4aa1639b4892b0faeedb4b9df4c6c7ac2b20d299])
*
ambari-server/src/test/java/org/apache/ambari/server/alerts/StaleAlertRunnableTest.java
* ambari-server/src/main/resources/alerts.json
*
ambari-server/src/main/java/org/apache/ambari/server/alerts/AmbariPerformanceRunnable.java
* ambari-server/src/main/java/org/apache/ambari/server/alerts/AlertRunnable.java
*
ambari-server/src/main/java/org/apache/ambari/server/alerts/StaleAlertRunnable.java
> 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)
