[
https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jian He updated YARN-4519:
--
Fix Version/s: (was: 2.9.0)
2.8.0
> potential deadlock of CapacityScheduler between
[
https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jian He updated YARN-4519:
--
Target Version/s: 2.8.0 (was: 2.9.0)
> potential deadlock of CapacityScheduler between decrease container and
[
https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
MENG DING updated YARN-4519:
Attachment: YARN-4519.3.patch
[~jianhe] and I had a discussion offline. Instead of grabbing the CS lock for
[
https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
MENG DING updated YARN-4519:
Attachment: YARN-4519.2.patch
Attaching new patch that addressed the failed test case.
We only need to
[
https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
MENG DING updated YARN-4519:
Attachment: YARN-4519.1.patch
Attaching the latest patch that addresses this issue:
bq. We need to make
[
https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-4519:
---
Description:
In CapacityScheduler.allocate() , first get FiCaSchedulerApp sync lock, and may
be get
