Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <19972349.47901283832752785.JavaMail.jira@thor>
Date: Tue, 7 Sep 2010 00:12:32 -0400 (EDT)
From: "Amareshwari Sriramadasu (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-1582) JobClient#monitorAndPrintJob()
 should use logger for logging taskDiagnostics
In-Reply-To: <74446978.152431268132007299.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Amareshwari Sriramadasu updated MAPREDUCE-1582:
-----------------------------------------------

    Status: Open  (was: Patch Available)

Johannes, The patch does not apply to trunk. Can you upload the patch for trunk? In trunk, changes should go into org.apache.hadoop.mapreduce.Job 

> JobClient#monitorAndPrintJob() should use logger for logging taskDiagnostics
> ----------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1582
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1582
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: job submission
>            Reporter: Johannes Zillmann
>            Priority: Minor
>         Attachments: MAPREDUCE-1582.patch
>
>
> In JobClient#monitorAndPrintJob() (around line 1324 in version 0.20.1) the exception of tasktrackers are printed via system.err.
> Using LOG.error() instead would make capturing the logs easier !

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.