hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matei Zaharia (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5154) 4-way deadlock in FairShare scheduler
Date Sat, 14 Feb 2009 20:25:59 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Matei Zaharia updated HADOOP-5154:

    Attachment: hadoop-5154-v2.patch

Updated this patch a little so it will continue working after we commit HADOOP-4665. In 4665
(the preemption patch), the update() method in the FairScheduler needs a lock on the JobTracker
to be able to call killTasks. However, since the JobTracker locks itself before locking the
FairScheduler in its assignTasks logic, the lock order has to be JobTracker then FairScheduler
(otherwise we'd get a deadlock). Therefore update() also locks first the JT and then the FairScheduler.
I've modified this patch to ensure that the two pieces of code that call scheduler.update()
do the same.

> 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
>         Attachments: FairSchedulerDeadLock.txt, hadoop-5154-v0.patch, hadoop-5154-v1.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