Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <16945295.1146544187087.JavaMail.jira@brutus>
Date: Tue, 2 May 2006 04:29:47 +0000 (GMT+00:00)
From: "Owen O'Malley (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-186) communication problems in the task
 tracker cause long latency
In-Reply-To: <18785389.1146543706369.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/HADOOP-186?page=comments#action_12377316 ] 

Owen O'Malley commented on HADOOP-186:
--------------------------------------

I should add that there are other, as yet undiscovered sources of long latency in the TaskTracker. We've seen pings and progress calls that take 5 minutes to complete. This patch does not solve that problem at all.

> 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