[
https://issues.apache.org/jira/browse/AMBARI-14565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-14565:
-------------------------------------
Attachment: AMBARI-14565.patch
> Renaming cluster in Ambari breaks alerts
> ----------------------------------------
>
> Key: AMBARI-14565
> URL: https://issues.apache.org/jira/browse/AMBARI-14565
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.4.0
>
> Attachments: AMBARI-14565.patch
>
>
> After renaming a cluster using the admin view, the following error messages
> are seen in the logs:
> HeartBeatHandler:306 - Unable to process alerts because the cluster Analytics
> does not exist
> hdpm-m610-3-ambari-server.log:28 Jul 2015 14:45:42,960 WARN
> [qtp-ambari-agent-325199] HeartBeatHandler:306 - Unable to process alerts
> because the cluster Analytics does not exist
> hdpm-m610-3-ambari-server.log:28 Jul 2015 14:45:42,960 WARN
> [qtp-ambari-agent-325199]
> This is because the hash for the alert definitions never changes and the
> alert jobs are never rescheduled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
