[
https://issues.apache.org/jira/browse/MAPREDUCE-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14245807#comment-14245807
]
Harsh J commented on MAPREDUCE-6194:
------------------------------------
If someone would like to try working on this, the file to edit is
{{hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/MapTask.java}},
and essentially we'd want some variable storing the last WARNed exception and
rethrowing that at the end with a wrapped message such as "Final error in
constructing the collector was:".
A more clever impl. could include messages from each of the attempt exceptions,
collecting them all, but the above would usually do for most of users only
using the standard single/pair of collectors.
> Bubble up final exception in failures during creation of output collectors
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-6194
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6194
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: task
> Affects Versions: 2.6.0
> Reporter: Harsh J
> Priority: Minor
> Labels: newbie
>
> MAPREDUCE-5974 added in ability to instantiate multiple OCs, but if none of
> them are able to load it "throws" only a final a generic message: {{"Unable
> to initialize any output collector"}}
> The older behaviour was to throw the actual instantiation exception back, so
> it makes it to client logs with an actual meaningful error.
> Now the clients need to go take a look at the task's logs to find the WARNs
> that represent the failure in instantiation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
