hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-6194) Bubble up final exception in failures during creation of output collectors
Date Mon, 15 Dec 2014 08:56:14 GMT

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

Harsh J updated MAPREDUCE-6194:
-------------------------------
    Target Version/s: 2.7.0
        Hadoop Flags: Reviewed

Looks good to me, thanks very much Varun! Committing shortly.

P.s. Please do not set a 'Fix Version', instead use the 'Target Version'. The former is used
by the project to indicate which versions it has _already been_ committed to, while the latter
is for which version it _needs to be_ committed to.

> 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
>            Assignee: Varun Saxena
>            Priority: Minor
>              Labels: newbie
>         Attachments: MAPREDUCE-6194.patch
>
>
> 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)

Mime
View raw message