[ https://issues.apache.org/jira/browse/YARN-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14355766#comment-14355766 ]
Wangda Tan commented on YARN-3215: ---------------------------------- One possible failed case is like https://issues.apache.org/jira/browse/YARN-2008. When we have hierarchy of labeled queues, CS can report incorrect headroom to AM which can cause problems. I haven't reproduced/tested this issue, but label-based headroom calculation is not supported now. > Respect labels in CapacityScheduler when computing headroom > ----------------------------------------------------------- > > Key: YARN-3215 > URL: https://issues.apache.org/jira/browse/YARN-3215 > Project: Hadoop YARN > Issue Type: Sub-task > Components: capacityscheduler > Reporter: Wangda Tan > Assignee: Wangda Tan > > In existing CapacityScheduler, when computing headroom of an application, it > will only consider "non-labeled" nodes of this application. > But it is possible the application is asking for labeled resources, so > headroom-by-label (like 5G resource available under node-label=red) is > required to get better resource allocation and avoid deadlocks such as > MAPREDUCE-5928. > This JIRA could involve both API changes (such as adding a > label-to-available-resource map in AllocateResponse) and also internal > changes in CapacityScheduler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)