ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8934) Blueprints: Deploying Blueprint with Hive fails due to ordering issues
Date Mon, 29 Dec 2014 03:04:13 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259806#comment-14259806
] 

Hudson commented on AMBARI-8934:
--------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #1348 (See [https://builds.apache.org/job/Ambari-trunk-Commit/1348/])
AMBARI-8934. Fix event handling for Hive deployments in Blueprints. (rnettleton) (rnettleton:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9c73f2cbba3e0d0cb6a6f9e8e94ef6c830afcbf4)
* ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java


> Blueprints: Deploying Blueprint with Hive fails due to ordering issues
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-8934
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8934
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8934.patch
>
>
> Attempting to deploy a Blueprint that includes HIVE is currently broken.  
> When the server attempts to install/startup the MYSQL_SERVER component, the following
exception is logged in ambari-server.log:
> 03:01:16,381  INFO [qtp565252965-94] HeartBeatHandler:551 - State of service component
MYSQL_SERVER of service HIVE of cluster clusterone has changed from INSTALLED to STARTED at
host c6401.ambari.apache.org
> 03:02:25,117 ERROR [Thread-20] ClusterImpl:2331 - Invalid transition
> org.apache.ambari.server.state.fsm.InvalidStateTransitionException: Invalid event: HOST_SVCCOMP_START
at STARTED
> at org.apache.ambari.server.state.fsm.StateMachineFactory.doTransition(StateMachineFactory.java:297)
> 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.svccomphost.ServiceComponentHostImpl.handleEvent(ServiceComponentHostImpl.java:886)
> at org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:60)
> at org.apache.ambari.server.state.cluster.ClusterImpl.processServiceComponentHostEvents(ClusterImpl.java:2326)
> at org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterce
> Recent stack defintion refactorings in the Hive area seem to have somehow modified the
ordering in which services start. In addition, the Hive "MYSQL_SERVER" component appears to
startup at install time.  This triggers the ambari-server's HeartbeatHandler to set the component's
state directly, which causes the above exception in the state machine code.  
> I'm working on a fix for this, and will be submitting a patch shortly.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message