hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (HADOOP-436) Concluding that the Map task failed may not be always right in getMapOutput.jsp
Date Thu, 10 Aug 2006 13:39:14 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-436?page=all ]

Devaraj Das reassigned HADOOP-436:
----------------------------------

    Assignee: Devaraj Das

> Concluding that the Map task failed may not be always right in getMapOutput.jsp
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-436
>                 URL: http://issues.apache.org/jira/browse/HADOOP-436
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Devaraj Das
>         Assigned To: Devaraj Das
>
> In the getMapOutput.jsp, tracker.mapOutputLost is called irrespective of whether the
sender of the map output threw an exception or the receiver died (thereby closing the socket
causing the jsp to throw an exception). Invoking the method causes the corresponding map task
to fail and causes it to be rescheduled but it may be the case that the problem is at the
reciever's end. Need to do a better check of where the exception was thrown.

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

        

Mime
View raw message