You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2016/03/10 06:20:40 UTC

[jira] [Issue Comment Deleted] (TEZ-3148) Invalid event TA_TEZ_EVENT_UPDATE on TaskAttempt

     [ https://issues.apache.org/jira/browse/TEZ-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hitesh Shah updated TEZ-3148:
-----------------------------
    Comment: was deleted

(was: [~ozawa] Agree with [~aplusplus] - TA_TEZ_EVENT_UPDATE represents data movement events, etc sent by the task to the AM. These events should always be seen before a task reaches its final completed state. If we see any event after a completed state, then this likely implies a bug. 

With that in mind, I think restricting the transitions to just kill in progress and fail in progress and ignoring these events in those transitions should be ok. )

> Invalid event TA_TEZ_EVENT_UPDATE on TaskAttempt
> ------------------------------------------------
>
>                 Key: TEZ-3148
>                 URL: https://issues.apache.org/jira/browse/TEZ-3148
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Rajesh Balamohan
>            Assignee: Tsuyoshi Ozawa
>         Attachments: TEZ-3148.001.patch, am.log.gz, dag.dot
>
>
> Got the following when executing one of the DAG. 
> Tez details:
> versionInfo=[ component=tez-dag, version=0.8.3-SNAPSHOT, revision=3e409ae0ee7233b4cf631cac1bc366679a08b7d1, SCM-URL=scm:git:https://git-wip-us.apache.org/repos/asf/tez.git, buildTime=20160227-1912]
> {noformat}
> Invalid event TA_TEZ_EVENT_UPDATE on TaskAttempt attempt_1455662455106_2317_27_02_000339_0
> FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.tez.TezTask. Invalid event TA_TEZ_EVENT_UPDATE on TaskAttempt attempt_1455662455106_2317_27_02_000339_0
> Exception in thread "75b0f971-7f89-461a-b432-45e1ac6e374b main" java.lang.AbstractMethodError: org.apache.tez.dag.history.ats.acls.ATSHistoryACLPolicyManager.close()V
>         at org.apache.tez.client.TezClient.stop(TezClient.java:562)
>         at org.apache.hadoop.hive.ql.exec.tez.TezSessionState.closeClient(TezSessionState.java:474)
>         at org.apache.hadoop.hive.ql.exec.tez.TezSessionState.close(TezSessionState.java:436)
>         at org.apache.hadoop.hive.ql.exec.tez.TezSessionPoolManager.closeIfNotDefault(TezSessionPoolManager.java:338)
>         at org.apache.hadoop.hive.ql.session.SessionState.close(SessionState.java:1469)
>         at org.apache.hadoop.hive.cli.CliSessionState.close(CliSessionState.java:66)
>         at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:719)
>         at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:645)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:497)
>         at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
>         at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> {noformat}
> Additional note for later reference: Q51 in tpcds can possibly be used to reproduce this at 10 TB scale.



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