ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <>
Subject [jira] [Commented] (AMBARI-15647) Alerts Using the SKIPPED State Cause Stale Alert Notification
Date Thu, 31 Mar 2016 14:00:32 GMT


Jonathan Hurley commented on AMBARI-15647:

I believe that the only alerts which current use the SKIPPED state are the HDFS "deviation"
alerts specified here:

But any custom created script could also be using it as well. 

> Alerts Using the SKIPPED State Cause Stale Alert Notification
> -------------------------------------------------------------
>                 Key: AMBARI-15647
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: 2.4.0
> 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):[NameNode Service RPC
Queue Latency (Hourly) (2h 18m), NameNode Service RPC Processing Latency (Hourly) (2h 18m)]
> {code}

This message was sent by Atlassian JIRA

View raw message