You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/02/16 13:17:02 UTC
[jira] [Commented] (AMBARI-22289) Alert definition update event
creation was failed with AmbariException on alert definition registration
[ https://issues.apache.org/jira/browse/AMBARI-22289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367241#comment-16367241 ]
Hudson commented on AMBARI-22289:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8744 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8744/])
AMBARI-22289. Alert definition update event creation was failed with (mpapyrkovskyy: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=ada8f83b7efe874e5354111458715c8a14a94e7b])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/stomp/AlertDefinitionsHolder.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/events/AlertDefinitionsUpdateEvent.java
> Alert definition update event creation was failed with AmbariException on alert definition registration
> -------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-22289
> URL: https://issues.apache.org/jira/browse/AMBARI-22289
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 3.0.0
> Reporter: Myroslav Papirkovskyi
> Assignee: Myroslav Papirkovskyi
> Priority: Critical
> Fix For: 3.0.0
>
>
> During cluster deploy numerous exceptions were posted in server logs:
> {code}
> org.apache.ambari.server.AmbariException: Unknown clusters in update
> at org.apache.ambari.server.agent.stomp.AlertDefinitionsHolder.handleUpdate(AlertDefinitionsHolder.java:105)
> at org.apache.ambari.server.agent.stomp.AlertDefinitionsHolder.handleUpdate(AlertDefinitionsHolder.java:53)
> at org.apache.ambari.server.agent.stomp.AgentHostDataHolder.updateData(AgentHostDataHolder.java:69)
> at org.apache.ambari.server.agent.stomp.AlertDefinitionsHolder.safelyUpdateData(AlertDefinitionsHolder.java:191)
> at org.apache.ambari.server.agent.stomp.AlertDefinitionsHolder.handleSingleDefinitionChange(AlertDefinitionsHolder.java:212)
> at org.apache.ambari.server.agent.stomp.AlertDefinitionsHolder.onAlertDefinitionRegistered(AlertDefinitionsHolder.java:132)
> at sun.reflect.GeneratedMethodAccessor283.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
> at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47)
> at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
> at com.google.common.eventbus.AsyncEventBus.access$001(AsyncEventBus.java:34)
> at com.google.common.eventbus.AsyncEventBus$1.run(AsyncEventBus.java:117)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> This was caused by an attempt to update non-existent AlertCluster in AlertDefinitionsHolder.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)