(RESEND, MENT TO ATTACH THE COMMENT BELOW TO THIS POSTING)
Why don't we include documenting this as part of the the "map-reduce
walk-through" sprint item?
-----
On reintegrating lost task trackers...
It does seem like we should do this to me, but we need to make sure
we reason through how this effects corner cases, what invariants the
system does maintain and so on.
I suggest we work this through, and then go forward with this patch
(modified if we find any corner cases) and post the reasoning, so we
can review it as this logic evolves. (And update any existing
documentation in this area of course...)
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
