You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Bing Jiang (JIRA)" <ji...@apache.org> on 2014/07/31 05:22:38 UTC

[jira] [Updated] (MAPREDUCE-6015) Make MR ApplicationMaster disable loading user's jars firstly

     [ https://issues.apache.org/jira/browse/MAPREDUCE-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bing Jiang updated MAPREDUCE-6015:
----------------------------------

          Component/s: applicationmaster
    Affects Version/s: 2.4.1

> Make MR ApplicationMaster disable loading user's jars firstly 
> --------------------------------------------------------------
>
>                 Key: MAPREDUCE-6015
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6015
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: applicationmaster
>    Affects Versions: 2.4.1
>            Reporter: Bing Jiang
>
> In most cases, we want to use -Dmapreduce.user.classpath.first=true to pick user's jars ahead of hadoop system's jars, which can make tasks run based upon the customized environment under the circumstance that hadoop system default library contains the different version of dependent jars.
> However, using -Dmapreduce.user.classpath.first=true will cause ApplicationMaster failure to launch due to conflicting classes.
> In most cases, if users do not customize the ApplicationMaster for MapReduce framework, I believe we can treat MRAppMaster different with MapTask/ReduceTask at the point of loading user's jar in classloader. 
> I believe it can provide  a property of  '-Dmapreduce.am.user.classpath.first=false'  to disable the feature of loading user's jars firstly. 
>  



--
This message was sent by Atlassian JIRA
(v6.2#6252)