[
https://issues.apache.org/jira/browse/AMBARI-15647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220715#comment-15220715
]
Hudson commented on AMBARI-15647:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.2 #577 (See
[https://builds.apache.org/job/Ambari-branch-2.2/577/])
AMBARI-15647 - Alerts Using the SKIPPED State Cause Stale Alert (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6c83a334140197b4da106540984711ed4eeff812])
* ambari-agent/src/main/python/ambari_agent/alerts/base_alert.py
*
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertReceivedListener.java
*
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertReceivedListenerTest.java
* ambari-server/src/main/java/org/apache/ambari/server/state/AlertState.java
* ambari-agent/src/test/python/ambari_agent/TestAlerts.py
> Alerts Using the SKIPPED State Cause Stale Alert Notification
> -------------------------------------------------------------
>
> Key: AMBARI-15647
> URL: https://issues.apache.org/jira/browse/AMBARI-15647
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.4.0
>
> Attachments: AMBARI-15647.patch
>
>
> SCRIPT alerts which use the {{SKIPPED}} state as a way of preventing
> processing are causing instances of the Ambari Stale Alert to trigger. This
> is because the agents do not return these alerts in the heartbeat causing
> their timestamps not to update.
> STR:
> - Create a SCRIPT alert which returns {{SKIPPED}} as it's state.
> - Wait for the stale alert to trigger.
> {code}
> There are 1 stale alerts from 1 host(s): c6401.ambari.apache.org[NameNode
> Service RPC Queue Latency (Hourly) (2h 18m), NameNode Service RPC Processing
> Latency (Hourly) (2h 18m)]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
