[
https://issues.apache.org/jira/browse/HADOOP-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674884#action_12674884
]
Hemanth Yamijala commented on HADOOP-5154:
------------------------------------------
bq. The reason showJobs doesn't lock the JobTracker is because it only looks at
information in the fair scheduler.
Matei, we access {{JobTracker.runningJobs()}}. This is accessing the jobs data
structure in an unsynchronized manner. I see there's a
{{JobTracker.getRunningJobs()}} which is providing synchronized access.
I also meant that the scheduler instance is not being locked when accessing
APIs in the scheduler. Is that not required as well ?
bq. How is it (refresh) handled on the JobTracker's web UI? For some reason I
thought that refreshed.
The JobTracker web page is not refreshed. The Job and task details web pages
are, and I see that the Job details web page does not synchronize access to the
jobs data structure as well. But that is still a bug. *smile*.
> 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.
