You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sandor Magyari (JIRA)" <ji...@apache.org> on 2016/05/03 17:41:12 UTC
[jira] [Updated] (AMBARI-16225) Blueprint Deployed Clusters Throw
Exceptions On Startup
[ https://issues.apache.org/jira/browse/AMBARI-16225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandor Magyari updated AMBARI-16225:
------------------------------------
Attachment: AMBARI-16225.patch
> Blueprint Deployed Clusters Throw Exceptions On Startup
> -------------------------------------------------------
>
> Key: AMBARI-16225
> URL: https://issues.apache.org/jira/browse/AMBARI-16225
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: ambari-2.4.0
> Reporter: Sandor Magyari
> Assignee: Sandor Magyari
> Priority: Critical
> Fix For: ambari-2.4.0
>
> Attachments: AMBARI-16225.patch
>
>
> After deploying a cluster with standard services (ZK, HDFS, etc) using blueprints, when user restarts Ambari, there are exceptions like below as the server is starting up.
> {code}
> java.lang.NullPointerException
> at org.apache.ambari.server.controller.internal.Stack.<init>(Stack.java:164)
> at org.apache.ambari.server.topology.BlueprintImpl.parseStack(BlueprintImpl.java:292)
> at org.apache.ambari.server.topology.BlueprintImpl.<init>(BlueprintImpl.java:66)
> at org.apache.ambari.server.topology.BlueprintFactory.getBlueprint(BlueprintFactory.java:87)
> at org.apache.ambari.server.topology.PersistedStateImpl$ReplayedTopologyRequest.<init>(PersistedStateImpl.java:334)
> at org.apache.ambari.server.topology.PersistedStateImpl.getAllRequests(PersistedStateImpl.java:154)
> at org.apache.ambari.server.topology.TopologyManager.ensureInitialized(TopologyManager.java:126)
> at org.apache.ambari.server.topology.TopologyManager.onHostHeartBeatLost(TopologyManager.java:386)
> at org.apache.ambari.server.state.host.HostImpl$HostHeartbeatLostTransition.transition(HostImpl.java:408)
> at org.apache.ambari.server.state.host.HostImpl$HostHeartbeatLostTransition.transition(HostImpl.java:396)
> at org.apache.ambari.server.state.fsm.StateMachineFactory$SingleInternalArc.doTransition(StateMachineFactory.java:354)
> at org.apache.ambari.server.state.fsm.StateMachineFactory.doTransition(StateMachineFactory.java:294)
> at org.apache.ambari.server.state.fsm.StateMachineFactory.access$300(StateMachineFactory.java:39)
> at org.apache.ambari.server.state.fsm.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:440)
> at org.apache.ambari.server.state.host.HostImpl.handleEvent(HostImpl.java:584)
> at org.apache.ambari.server.agent.HeartbeatMonitor.doWork(HeartbeatMonitor.java:159)
> at org.apache.ambari.server.agent.HeartbeatMonitor.run(HeartbeatMonitor.java:120)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Looks like a the AMC is not initialized yet as the heartbeat from agents is being handled. It doesn't seem to affect operation of the cluster, but it looks really bad.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)