[
https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142162#comment-15142162
]
Hudson commented on YARN-4519:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #9280 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9280/])
Move YARN-4519 in CHANGES.txt to 2.8 (jianhe: rev
39a71b606a4abdc46ea6dfce2b79480b47ec18b5)
* hadoop-yarn-project/CHANGES.txt
> potential deadlock of CapacityScheduler between decrease container and assign
> containers
> ----------------------------------------------------------------------------------------
>
> Key: YARN-4519
> URL: https://issues.apache.org/jira/browse/YARN-4519
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Reporter: sandflee
> Assignee: MENG DING
> Fix For: 2.8.0
>
> Attachments: YARN-4519.1.patch, YARN-4519.2.patch, YARN-4519.3.patch
>
>
> In CapacityScheduler.allocate() , first get FiCaSchedulerApp sync lock, and
> may be get CapacityScheduler's sync lock in decreaseContainer()
> In scheduler thread, first get CapacityScheduler's sync lock in
> allocateContainersToNode(), and may get FiCaSchedulerApp sync lock in
> FicaSchedulerApp.assignContainers().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
