You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2006/05/02 20:19:06 UTC
[jira] Resolved: (HADOOP-186) communication problems in the task
tracker cause long latency
[ http://issues.apache.org/jira/browse/HADOOP-186?page=all ]
Doug Cutting resolved HADOOP-186:
---------------------------------
Resolution: Fixed
I just committed this. Thanks, Owen!
> communication problems in the task tracker cause long latency
> -------------------------------------------------------------
>
> Key: HADOOP-186
> URL: http://issues.apache.org/jira/browse/HADOOP-186
> Project: Hadoop
> Type: Bug
> Components: mapred
> Versions: 0.1.1
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 0.2
> Attachments: task-tracker-loop-isolation.patch
>
> The Task Tracker's offerService loop has no protection from exceptions, so that any communication problems with the Job Tracker, such as RPC timeouts, cause the TaskTracker to sleep 5 seconds and start again at the top of the loop.
--
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