hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3215) Respect labels in CapacityScheduler when computing headroom
Date Thu, 28 Jan 2016 03:25:40 GMT

    [ https://issues.apache.org/jira/browse/YARN-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120685#comment-15120685
] 

Sunil G commented on YARN-3215:
-------------------------------

Yes [~leftnoteasy], Thanks for pointing out. Current approach will return 0 in this initial
case . I think a general safe approach (more headroom can be assumed safe for now) is what
looks suits here considering some corner scenarios like this. With clear long term approach
"by-partition headroom" ahead, as you mentioned all this can be handled. Till then, i think
its safer to assume NO_LABEL in default case.

> 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, YARN-3215.v2.001.patch, YARN-3215.v2.002.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)

Mime
View raw message