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 Wed, 18 Feb 2009 17:31:04 GMT

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

Hemanth Yamijala commented on HADOOP-5154:
------------------------------------------

Matei, couple of comments:

- I see you are now locking on the JobTracker and then the scheduler. The Fairscheduler web
UI has refresh turned on by default. I am wondering if this can cause excessive lock contention
with the JT, which could affect the JT code - like scheduling, etc. Maybe the refresh should
be turned off by default, and enabled with a large refresh period on demand ?

- Doesn't showJobs also need synchronization on the JobTracker and scheduler ?

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