[
https://issues.apache.org/jira/browse/TEZ-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875277#comment-13875277
]
Siddharth Seth commented on TEZ-740:
------------------------------------
Commit message is TEZ-140 instead of TEZ-740. Any idea if we can change this ?,
since the change-log will likely be generated from the commit log.
> Tez/hive task failure on large DAG with Invalid event: TA_SCHEDULE at KILLED
> ----------------------------------------------------------------------------
>
> Key: TEZ-740
> URL: https://issues.apache.org/jira/browse/TEZ-740
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.2.0
> Reporter: Gopal V
> Assignee: Bikas Saha
> Fix For: 0.3.0
>
> Attachments: TA_SCHEDULE.log.tgz, TEZ-740.1.patch
>
>
> The Tez AM exits with the following error and kills the query
> {code}
> 2014-01-16 22:18:14,661 ERROR [AsyncDispatcher event handler]
> org.apache.tez.dag.app.dag.impl.TaskAttemptImpl: Can't handle this event at
> current state for attempt_1389745080241_0038_1_01_000096_2
> org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event:
> TA_SCHEDULE at KILLED
> {code}
> Another attempt had died on an Exception
> {code}
> org.apache.tez.dag.app.dag.impl.TaskAttemptImpl:
> attempt_1389745080241_0038_1_13_000114_2 TaskAttempt Transitioned from
> RUNNING to FAIL_IN_PROGRESS
> {code}
> Looks like a mapper failed and the reducer went from NEW to KILLED, but got a
> TA_SCHEDULE after entering KILLED.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
