hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5814) fat jar with *-default.xml may fail when mapreduce.job.classloader=true.
Date Fri, 28 Mar 2014 03:43:15 GMT

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

Sangjin Lee commented on MAPREDUCE-5814:
----------------------------------------

Sounds good. I agree users adding *-site.xml files in their jar is such an edge case that
I don't think we need to be defensive about that type of scenarios as well. The *-default.xml
files can definitely get in via build, but not *-site.xml...

> fat jar with *-default.xml may fail when mapreduce.job.classloader=true.
> ------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5814
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5814
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 2.3.0
>            Reporter: Gera Shegalov
>            Assignee: Gera Shegalov
>         Attachments: MAPREDUCE-5814.v01.patch
>
>
> We faced a failure when a job.jar compiled against 0.20+ hadoop artifacts had to run
with {{mapreduce.job.classloader=true}} because it needed a more recent guava as a dependency.
The job failed because the cluster's {{*-default.xml}} files were overshadowed by the ones
in the fat jar. We propose to treat these default config files like the system packages {{org.apache.hadoop.}}
to avoid a counterintuitivie behavior as if we had {{mapreduce.job.user.classpath.first}}
set.



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

Mime
View raw message