[
https://issues.apache.org/jira/browse/MAPREDUCE-7172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040460#comment-17040460
]
Jim Brennan commented on MAPREDUCE-7172:
----------------------------------------
[~leftnoteasy], [~templedf] any update on this? While running regression tests
on branch-2.10 with our grid data management tool, it looks like we hit a
similar issue. I've found that setting
{{mapreduce.client.libjars.wildcard=false}} fixes it.
In the case that was failing for us, tmpjars had:
{noformat}
/user/dfsload/.gdm/gq1/replication/opengdm/shipjars/replication-core.jar,
/user/dfsload/.gdm/gq1/replication/opengdm/jobjars/replication-distcopy.jar
/user/dfsload/.gdm/gq1/replication/opengdm/jobjars/acquisition-loader.jar,
etc...
{noformat}
But mapreduce.job.cache.files was just
"hdfs://n2:8020/user/dfsload/.staging/job_1581958257895_0005/libjars/*"
and we were failing on a classNotFound exception.
> Wildcard functionality of -libjar is broken when jars are located in same
> remote FS
> -----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-7172
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7172
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Wangda Tan
> Priority: Critical
>
> We recently found that when -libjar specified jars on the same remote FS,
> jars will not be properly added to classpath.
> The reason is MAPREDUCE-6719 added the wildcard functionality, but the follow
> logic assumes files are all placed under job's submission directory. (Inside
> JobResourceUploader)
> {code:java}
> if (useWildcard && !foundFragment) {
> // Add the whole directory to the cache using a wild card
> Path libJarsDirWildcard =
> jtFs.makeQualified(new Path(libjarsDir, DistributedCache.WILDCARD));
> DistributedCache.addCacheFile(libJarsDirWildcard.toUri(), conf);
> }{code}
> However, in the same method, specified resources will be only uploaded when
> two FSes are different, see copyRemoteFiles:
> {code:java}
> if (FileUtil.compareFs(remoteFs, jtFs)) {
> return originalPath;
> } {code}
> Workaround of this issue is pass:
> mapreduce.client.libjars.wildcard = false.
> When the MR job got launched.
> Example commandline to reproduce this issue is:
> {code:java}
> hadoop jar abc.jar org.ABC -libjars
> "wasb://host/path1/jar1,wasb://host/path2/jar2..."{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
