hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "eric baldeschwieler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-181) task trackers should not restart for having a late heartbeat
Date Thu, 10 Aug 2006 23:28:16 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-181?page=comments#action_12427371 ] 
eric baldeschwieler commented on HADOOP-181:

Oh a whole thread can be had on this I'm sure!

Why does one turn off speculative execution?  Presumably because a MAP has unmanaged side-effects?

But... the framework still will rerun jobs if they complete and then the node is lost, right?
 Won't this tickle exactly the same issues that speculative execution raised anyway?

Doesn't this imply that disallowing speculative execution is basically not the right mechanism
to deal with the side-effect issue and that this deserves a rethink?

> task trackers should not restart for having a late heartbeat
> ------------------------------------------------------------
>                 Key: HADOOP-181
>                 URL: http://issues.apache.org/jira/browse/HADOOP-181
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Owen O'Malley
>         Assigned To: Devaraj Das
>             Fix For: 0.6.0
>         Attachments: lost-heartbeat.patch
> TaskTrackers should not close and restart themselves for having a late heartbeat. The
JobTracker should just accept their current status.

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


View raw message