Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

difference between 'mapreduce.application.classpath' and 'yarn.application.classpath'

avatar
Contributor

Hi All, it may be a trivial question for many, but could you explain what is the difference or relation between classpath defined in yarn.application.classpath and mapreduce.application.classpath? Does the latter overwrite the former for mapreduce applications? There is also variable MR2_CLASSPATH that is included by default in mapreduce.application.classpath. Where is taken from? Is the mapreduce.application.classpath relevant only for gateways from were application is submitted to yarn?

1 ACCEPTED SOLUTION

avatar
Mentor
hide-solution

This problem has been solved!

Want to get a detailed solution you have to login/registered on the community

Register/Login
4 REPLIES 4

avatar
Mentor
hide-solution

This problem has been solved!

Want to get a detailed solution you have to login/registered on the community

Register/Login

avatar
Contributor

Hello @Harsh J,

 

thanks you very much for your explanations. I asked the question starting with some assumptions that turned out to be false. Thanks for showing the right answers. Last question from my side: could you point to the documentation where mentioned CM 6.x feature for supplying framework jars is described? It sounds interesting.

avatar
Mentor
The feature in C6.x is implicit and aimed to support easier rolling
upgrades (when the job jars are part of the job exclusively, changes to
locally installed binaries will not affect it during upgrades). A release
note item is documented here for this:
https://www.cloudera.com/documentation/enterprise/6/release-notes/topics/rg_cm_600_new_features.html...

avatar
Contributor

Great! Thank you very much!