Looks like Coopr missed some locations from yarn.application.classpath property

Description

In the Coopr deployed cluster property set to:
<property>
<name>yarn.application.classpath</name>
<value>/etc/hadoop/conf,/usr/lib/hadoop/lib/,/usr/lib/hadoop/,/usr/hdp/current/hadoop-hdfs-namenode/,/usr/hdp/current/hadoop-hdfs-namenode/lib/,/usr/hdp/current/hadoop-hdfs-namenode/,/usr/hdp/current/hadoop-yarn-nodemanager/lib/,/usr/hdp/current/hadoop-yarn-nodemanager/,/usr/hdp/current/hadoop-mapreduce-historyserver/lib/,/usr/hdp/current/hadoop-mapreduce-historyserver/</value>
</property>

On cleanly installed cluster by Ambari:
<property>
<name>yarn.application.classpath</name>
<value>$HADOOP_CONF_DIR,/usr/hdp/current/hadoop-client/,/usr/hdp/current/hadoop-client/lib/,/usr/hdp/current/hadoop-hdfs-client/,/usr/hdp/current/hadoop-hdfs-client/lib/,/usr/hdp/current/hadoop-yarn-client/,/usr/hdp/current/hadoop-yarn-client/lib/</value>
</property>

It was discovered that on Coopr cluster hadoop-common.jar missed in the classpath. It is located in /usr/hdp/current/hadoop-client/*, but htis location missed from the property.
as a result, CDAP master can not start underneath containers.

Adding /usr/hdp/current/hadoop-client/* to the property solves the problem.

Release Notes

None

Activity

Show:
Leonid Fedotov
March 8, 2017, 11:55 PM

Not relevant.

Won't Fix
Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Bhooshan Mogal

Reporter

Leonid Fedotov

Labels