hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Dahiya (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-506) job tracker hangs on to dead task trackers "forever"
Date Thu, 05 Oct 2006 20:48:21 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-506?page=all ]

Sanjay Dahiya updated HADOOP-506:

           Status: Patch Available  (was: In Progress)
    Fix Version/s: 0.7.0

> job tracker hangs on to dead task trackers "forever"
> ----------------------------------------------------
>                 Key: HADOOP-506
>                 URL: http://issues.apache.org/jira/browse/HADOOP-506
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Yoram Arnon
>         Assigned To: Sanjay Dahiya
>            Priority: Minor
>             Fix For: 0.7.0
>         Attachments: Hadoop-506.patch
> I see cases where a task tracker gets disconnected from the job tracker and disconnects,
and then appears twice in the job tracker's list, with one instance being alive and well,
and the other's 'time since last heartbeat' increasing monotonically.
> that all makes sense.
> What doesn't make sense, is that the old instances never expire. It's been over 400000
seoncds since the last heartbeat. And the cluster reports having more nodes up and running
than its size (350 nodes in a 320 node cluster).
> there should be some reasonable timout for these expired task trackers, somewhere between
10 minutes and an hour.

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