hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5403) Get rid of yarn.application.classpath
Date Mon, 22 Jul 2013 22:10:48 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715757#comment-13715757

Sandy Ryza commented on MAPREDUCE-5403:

I don't think yarn.resourcemanager.address should be an environment variable.  I think there
is a conceptual difference between a client knowing how to contact a service and a client
knowing about details of the service's internals.  Do you disagree?

In an ideal world, I think should be able to point my application at a YARN cluster without
thinking about where the YARN jars were installed.  I understand that for MR we will still
not entirely have achieved this ideal, because the client still needs to know where the MR
jars are. But the change would be a step in the right direction and help lay the groundwork
for a solution by untangling the application from the framework.
> Get rid of yarn.application.classpath
> -------------------------------------
>                 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
> 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

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

View raw message