Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <9499391.1160590116196.JavaMail.jira@brutus>
Date: Wed, 11 Oct 2006 11:08:36 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-597) transmission errors to the reduce
 will cause map output to be considered lost
In-Reply-To: <18614380.1160585915012.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/HADOOP-597?page=comments#action_12441520 ] 
            
Doug Cutting commented on HADOOP-597:
-------------------------------------

Half the number of try/catch blocks would be required if you instead wrapped the outStream operations and use a badOutput boolean, no?

> transmission errors to the reduce will cause map output to be considered lost
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-597
>                 URL: http://issues.apache.org/jira/browse/HADOOP-597
>             Project: Hadoop
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Owen O'Malley
>         Assigned To: Owen O'Malley
>             Fix For: 0.7.1
>
>         Attachments: map-output-protect.patch
>
>
> When the mapOutput servlet gets an IOException from reading the map output file, it correctly declares the map output lost. However, an IOException writing to the socket should NOT cause the map output to be declared lost. Unfortunately, the current implementation always declares the map output lost. When the map output is lost, the map is re-run on a different computer.

-- 
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