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/04/18 21:49:27 UTC
[jira] Updated: (HADOOP-135) Potential deadlock in JobTracker.
[ http://issues.apache.org/jira/browse/HADOOP-135?page=all ]
Doug Cutting updated HADOOP-135:
--------------------------------
Component: mapred
> Potential deadlock in JobTracker.
> ---------------------------------
>
> Key: HADOOP-135
> URL: http://issues.apache.org/jira/browse/HADOOP-135
> Project: Hadoop
> Type: Bug
> Components: mapred
> Reporter: Konstantin Shvachko
>
> org.apache.hadoop.mapred.JobTracker.RetireJobs.run()
> locks resources in this order
> synchronized (jobs) {
> synchronized (jobInitQueue) {
> synchronized (jobsByArrival) {
> org.apache.hadoop.mapred.JobTracker.submitJob()
> locks resources in a different order
> synchronized (jobs) {
> synchronized (jobsByArrival) {
> synchronized (jobInitQueue) {
> This potentially can lead to a deadlock.
> Unless there is common lock on top of it in which case these
> three locks are redundant.
--
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