[ https://issues.apache.org/jira/browse/YARN-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093345#comment-15093345 ]
Wangda Tan commented on YARN-3215: ---------------------------------- Thanks [~Naganarasimha], Took a quick look at approach in the patch. My only concern is, now every application headroom computation needs at least O(number-of-priorities). Instead of computing requesting partitions, could we simply return "requested" partitions, which could save the loop to traverse all priorities. Thoughts? > 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: Naganarasimha G R > Attachments: YARN-3215.v1.001.patch > > > 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)