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

Vinay commented on TEZ-4074:
----------------------------

We were able to solve this issue by copying guava jar to the class path 


{code:java}
<property>
    <name>tez.am.launch.cluster-default.cmd-opts</name>
    <value>-cp /usr/hadoop/share/hadoop/hdfs/lib/guava-27.0-jre.jar:$CLASSPATH 
-server -Djava.net.preferIPv4Stack=true</value>
</property>
{code}
 

 

IMO, the above is a workaround, instead TEZ should adhere to the Hadoop class 
path first which has all the latest jar's (incase of Hadoop 3.x)

The main issue is the hive-exec jar which uses guava 11, the fix for which is 
being done here - https://issues.apache.org/jira/browse/HIVE-22126 

 

 

 

> Tez does not run with Hadoop Trunk (3.3.0-snapshot)
> ---------------------------------------------------
>
>                 Key: TEZ-4074
>                 URL: https://issues.apache.org/jira/browse/TEZ-4074
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Ahmed Hussein
>            Priority: Major
>
> Tez throws a runtime exception when compiled against Hadoop-3.3.0.
> With Tez running Guava (11.0.2) and Hadoop eunning Guava 27.0-jre (see 
> HADOOP-16210), there is an incompatibility of Guava library.
> {code:java}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.136 
> s <<< FAILURE! - in org.apache.tez.dag.app.TestSpeculation
> [ERROR] org.apache.tez.dag.app.TestSpeculation Time elapsed: 0.136 s <<< 
> ERROR!
> java.lang.NoSuchMethodError: 
> com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;Ljava/lang/Object;)V
> at 
> org.apache.tez.dag.app.TestSpeculation.setupSpeculation(TestSpeculation.java:86)
> {code}
> It looks like guava added single parameter optimizations which breaks 
> compatibility with {{VAR_ARGS}}. So, even though it shows source 
> compatibility it is throwing a runtime error due to binary incompatibility.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to