hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5154) 4-way deadlock in FairShare scheduler
Date Fri, 20 Feb 2009 05:27:02 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675247#action_12675247

Hemanth Yamijala commented on HADOOP-5154:

We access scheduler.infos and scheduler.getPoolManager. Since infos is being modified in the
scheduler code protected by the FairScheduler instance, this leads to inconsistent access.
Likewise, access to pool manager is being synchronized on the scheduler instance in other
methods. Basically, I am just looking at showJobs as being equivalent to showPools, and hence
should have the same synchronization constructs.

If you are modifying the patch to call getRunningJobs and introducing the synchronization
around the scheduler, please make sure that there's no inversion in the order of locking between
the scheduler and job tracker instances.

> 4-way deadlock in FairShare scheduler
> -------------------------------------
>                 Key: HADOOP-5154
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5154
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/fair-share
>            Reporter: Vinod K V
>            Assignee: Matei Zaharia
>            Priority: Blocker
>             Fix For: 0.18.4, 0.20.0
>         Attachments: FairSchedulerDeadLock.txt, hadoop-5154-v0.patch, hadoop-5154-v1.patch,
hadoop-5154-v2.patch, hadoop-5154-v3.patch
> This happened while trying to change the priority of a job from the scheduler servlet.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message