Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C9CE5CF86 for ; Sun, 14 Dec 2014 04:27:13 +0000 (UTC) Received: (qmail 49456 invoked by uid 500); 14 Dec 2014 04:27:13 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 49381 invoked by uid 500); 14 Dec 2014 04:27:13 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 49370 invoked by uid 99); 14 Dec 2014 04:27:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Dec 2014 04:27:13 +0000 Date: Sun, 14 Dec 2014 04:27:13 +0000 (UTC) From: "Harsh J (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MAPREDUCE-6194) Bubble up final exception in failures during creation of output collectors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated MAPREDUCE-6194: ------------------------------- Labels: newbie (was: ) > 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)