Created 10-24-2018 03:45 PM
Hi,
We have an application that requires Jackson-databind library with 2.4.4 or later. And, the application is hosted onto a HDP 2.6.5 Centos AWS 3 node cluster ( with Ambari and Oozie setup). During the job run we got below error:
On investigation we found that HDP setup has below 2.2.3 version.
../2.6.5.0-292/hadoop/lib/jackson-databind-2.2.3.jar
../2.6.5.0-292/hadoop/client/jackson-databind-2.2.3.jar
../2.6.5.0-292/hadoop/client/jackson-databind.jar
../2.6.5.0-292/hadoop-hdfs/lib/jackson-databind-2.2.3.jar
../2.6.5.0-292/hadoop-httpfs/webapps/webhdfs/WEB-INF/lib/jackson-databind-2.2.3.jar
../2.6.5.0-292/hadoop-yarn/lib/jackson-databind-2.2.3.jar
We had tried passing new jar as lib to the job configuration, and as per attached yarn logs, it is well shown but still MR action execution fails.
Can you please suggest, how to upgrade to 2.4.x ?
Or any possible work around to this issue.
Thanks.
Created 11-05-2018 01:39 PM
We are able to resolve the issue by applying below configurations on the Oozie action in xml.
<name>mapreduce.job.user.classpath.first</name>
<value>true</value>
</property>
<property>
<name>mapreduce.task.classpath.user.precedence</name>
<value>true</value>
</property>
<property>
<name>oozie.launcher.mapreduce.task.classpath.user.precedence</name>
<value>true</value>
</property>
<property>
<name>oozie.launcher.mapreduce.job.user.classpath.first</name>
<value>true</value>
</property>
To add, we got the reference of these properties from a related previous post. See below link.
Created 11-05-2018 01:39 PM
We are able to resolve the issue by applying below configurations on the Oozie action in xml.
<name>mapreduce.job.user.classpath.first</name>
<value>true</value>
</property>
<property>
<name>mapreduce.task.classpath.user.precedence</name>
<value>true</value>
</property>
<property>
<name>oozie.launcher.mapreduce.task.classpath.user.precedence</name>
<value>true</value>
</property>
<property>
<name>oozie.launcher.mapreduce.job.user.classpath.first</name>
<value>true</value>
</property>
To add, we got the reference of these properties from a related previous post. See below link.