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

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15179645#comment-15179645 ] 

TezQA commented on TEZ-3148:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12791425/TEZ-3148.001.patch
  against master revision 91e24d7.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 3.0.1) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/1543//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1543//console

This message is automatically generated.

> 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)