Why don't we include documenting this as part of the the "map-reduce
walk-through" sprint item?
-----
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?
On Aug 10, 2006, at 12:38 PM, Devaraj Das (JIRA) wrote:
[ http://issues.apache.org/jira/browse/HADOOP-181?
page=comments#action_12427327 ]
Devaraj Das commented on HADOOP-181:
------------------------------------
Doug, does it make sense to do what is done in this patch only when
speculative execution is on?
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
