[
https://issues.apache.org/jira/browse/MAPREDUCE-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718390#comment-13718390
]
Jason Lowe commented on MAPREDUCE-5403:
---------------------------------------
After looking at the patch, I tend to agree that this approach is probably
better long-term for managing the classpath. It's easier to access in general
and enables heterogeneous YARN deploys since the classpath is bound by the node
handling the container instead of the client. Specifically I'm thinking of the
rolling upgrades case where one node has the old YARN classpath layout and the
new YARN version has a different one. This hides that difference nicely.
I think the patch looks good overall, but we should document this somewhere
like
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/WritingYarnApplications.apt.vm.
> yarn.application.classpath requires client to know service internals
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-5403
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5403
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: client
> Affects Versions: 2.0.5-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: MAPREDUCE-5403.patch
>
>
> yarn.application.classpath is a confusing property because it is used by
> MapReduce and not YARN, and MapReduce already has
> mapreduce.application.classpath, which provides the same functionality.
--
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
