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 Fri, 06 Feb 2009 21:21:01 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-v0.patch

Thanks for finding this. Here's a patch that should fix it. It makes the FairSchedulerServlet
lock the scheduler rather than the poolManager, which is how the rest of the code works (JobTracker's
assignTasks, job listener stuff, and update thread). I haven't added any unit tests because
I don't know how one would write a unit test for this, but it's a pretty simple patch.

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


Mime
View raw message