You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2015/03/31 00:48:53 UTC
[jira] [Updated] (AMBARI-10285) Storm Shows An Alert for REST_API
Component After Stack Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley updated AMBARI-10285:
-------------------------------------
Attachment: AMBARI-10285.patch
> Storm Shows An Alert for REST_API Component After Stack Upgrade
> ---------------------------------------------------------------
>
> Key: AMBARI-10285
> URL: https://issues.apache.org/jira/browse/AMBARI-10285
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-10285.patch
>
>
> # Upgraded cluster with storm.
> # Noticed a CRITICAL alert named "Storm REST API". But there are no REST API components on stack 2.2. The alert is linking to host with Storm UI Server.
> The underlying problem here is that, indeed, Storm REST API was removed on HDP 2.2. However, Ambari doesn't remove the relationships in the database; it just modifies the in-memory stack definitions.
> As a result, the alerts framework still thinks there's a REST_API component installed on a host. In order to preserve the historical entires for that component, alerts will determine at startup the definitions which may no longer be valid and will disable them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)