[
https://issues.apache.org/jira/browse/MAPREDUCE-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720036#comment-13720036
]
Sandy Ryza commented on MAPREDUCE-4421:
---------------------------------------
Very cool. Would it make sense to allow directories as well in
mapreduce.application.framework.path? That would make it easier to swap out a
jar without rebuilding the tarball. Also, what would it take to make this work
easily for non-MR frameworks?
Does the distributed cache actually cache things in between jobs? The javadoc
says "Its efficiency stems from the fact that the files are only copied once
per job and the ability to cache archives which are un-archived on the slaves."
If so, we should probably modify the javadoc.
> Remove dependency on deployed MR jars
> -------------------------------------
>
> Key: MAPREDUCE-4421
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4421
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 2.0.0-alpha
> Reporter: Arun C Murthy
> Assignee: Jason Lowe
> Attachments: MAPREDUCE-4421.patch, MAPREDUCE-4421.patch
>
>
> Currently MR AM depends on MR jars being deployed on all nodes via implicit
> dependency on YARN_APPLICATION_CLASSPATH.
> We should stop adding mapreduce jars to YARN_APPLICATION_CLASSPATH and,
> probably, just rely on adding a shaded MR jar along with job.jar to the
> dist-cache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
