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/06/22 21:38:30 UTC

[jira] Resolved: (HADOOP-316) job tracker has a deadlock

     [ http://issues.apache.org/jira/browse/HADOOP-316?page=all ]
     
Doug Cutting resolved HADOOP-316:
---------------------------------

    Resolution: Fixed

I just committed this.  Thanks, Owen!

> job tracker has a deadlock
> --------------------------
>
>          Key: HADOOP-316
>          URL: http://issues.apache.org/jira/browse/HADOOP-316
>      Project: Hadoop
>         Type: Bug

>   Components: mapred
>     Versions: 0.3.2
>     Reporter: Owen O'Malley
>     Assignee: Owen O'Malley
>      Fix For: 0.4.0
>  Attachments: fix-expire-task-deadlock.patch
>
> The JobTracker has a deadlock in the ExpireLaunchingTasks stuff.
> In particular, it locks the JobTracker and launchingTasks inconsistently.
> This deadlocks has been observed in the wild and causes the JobTracker to stop responding to rpc and http (other than the root page).

-- 
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