[
https://issues.apache.org/jira/browse/MAPREDUCE-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497480#comment-14497480
]
Gera Shegalov commented on MAPREDUCE-6293:
------------------------------------------
In such a case It would be good to be able to reason what classloader is used
when job classloader is not set. Since we are already using the same approach
in other places where setCCL is called, I am +1. However, I think it will be be
helpful for debugging to add a LOG.info with thread and {{getCCL}} for
{{jobclassloader == nul}} cases as well. In {{CommitterEventHandler}} we don't
log at all.
> uberized job fails with the job classloader enabled
> ---------------------------------------------------
>
> Key: MAPREDUCE-6293
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6293
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mr-am
> Affects Versions: 2.6.0
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Attachments: MAPREDUCE-6293.001.patch
>
>
> An uberized job fails if the job classloader is enabled and the job needs to
> use the thread context classloader to load a class. Some example error in the
> log:
> {quote}
> 2015-03-23 23:28:34,675 INFO [main\]
> org.apache.hadoop.mapreduce.v2.util.MRApps: Creating job classloader
> ...
> 2015-03-23 23:28:42,096 ERROR [uber-SubtaskRunner\]
> cascading.provider.ServiceLoader: unable to find service class:
> cascading.tuple.hadoop.collect.HadoopTupleMapFactory, with exception:
> java.lang.ClassNotFoundException:
> cascading.tuple.hadoop.collect.HadoopTupleMapFactory
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
