Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 54047 invoked from network); 21 Apr 2006 01:23:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Apr 2006 01:23:10 -0000 Received: (qmail 76941 invoked by uid 500); 21 Apr 2006 01:23:10 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 76829 invoked by uid 500); 21 Apr 2006 01:23:09 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 76820 invoked by uid 99); 21 Apr 2006 01:23:09 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Apr 2006 18:23:09 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Apr 2006 18:23:08 -0700 Received: from brutus (localhost.localdomain [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 054997142E0 for ; Fri, 21 Apr 2006 01:22:06 +0000 (GMT) Message-ID: <13175945.1145582525991.JavaMail.jira@brutus> Date: Fri, 21 Apr 2006 01:22:05 +0000 (GMT+00:00) From: "Runping Qi (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Commented: (HADOOP-153) skip records that throw exceptions In-Reply-To: <25993970.1145554865659.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/HADOOP-153?page=comments#action_12375457 ] Runping Qi commented on HADOOP-153: ----------------------------------- +1 Exceptions in the map and reduce functions that are implemented by the user should be handled by the user within the functions. In the current implementation of sequencial file record reader, it is hard to skip to the next record if exception happens during record reading. > skip records that throw exceptions > ---------------------------------- > > Key: HADOOP-153 > URL: http://issues.apache.org/jira/browse/HADOOP-153 > Project: Hadoop > Type: New Feature > Components: mapred > Versions: 0.2 > Reporter: Doug Cutting > Assignee: Doug Cutting > Fix For: 0.2 > > MapReduce should skip records that throw exceptions. > If the exception is thrown under RecordReader.next() then RecordReader implementations should automatically skip to the start of a subsequent record. > Exceptions in map and reduce implementations can simply be logged, unless they happen under RecordWriter.write(). Cancelling partial output could be hard. So such output errors will still result in task failure. > This behaviour should be optional, but enabled by default. A count of errors per task and job should be maintained and displayed in the web ui. Perhaps if some percentage of records (>50%?) result in exceptions then the task should fail. This would stop jobs early that are misconfigured or have buggy code. > Thoughts? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira