[ 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
