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

Rajesh Balamohan commented on TEZ-1564:
---------------------------------------

No. It was one of the standard TPC-ds queries of hive (don't remember which one 
was that).  Haven't seen this issue with recent builds so far.

> State machine error: Invalid event: T_SCHEDULE at SCHEDULED
> -----------------------------------------------------------
>
>                 Key: TEZ-1564
>                 URL: https://issues.apache.org/jira/browse/TEZ-1564
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Rajesh Balamohan
>            Priority: Critical
>         Attachments: applogs.txt.tar.gz, dag.dot
>
>
> ERROR [AsyncDispatcher event handler] 
> org.apache.tez.dag.app.dag.impl.TaskImpl: Can't handle this event at current 
> state for task_1409722953518_0162_1_07_000000
> org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: 
> T_SCHEDULE at SCHEDULED
>       at 
> org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:305)
>       at 
> org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
>       at 
> org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
>       at org.apache.tez.dag.app.dag.impl.TaskImpl.handle(TaskImpl.java:827)
>       at org.apache.tez.dag.app.dag.impl.TaskImpl.handle(TaskImpl.java:95)
>       at 
> org.apache.tez.dag.app.DAGAppMaster$TaskEventDispatcher.handle(DAGAppMaster.java:1604)
>       at 
> org.apache.tez.dag.app.DAGAppMaster$TaskEventDispatcher.handle(DAGAppMaster.java:1590)
>       at 
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:173)
>       at 
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:106)
>       at java.lang.Thread.run(Thread.java:724)
> I will attach the dag + app logs soon.



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

Reply via email to