hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3215) Respect labels in CapacityScheduler when computing headroom
Date Wed, 30 Dec 2015 04:05:49 GMT

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

Naganarasimha G R commented on YARN-3215:
-----------------------------------------

Thanks for sharing your thoughts [~wangda],
bq.  I would suggest to delay the API change to 2.9 according to short timeframe for 2.8.
ok, thought so... just wanted to confirm.

bq. The first resource request of an app should be its AM request, we can at least get headroom
of the AM's partition. And returning headroom of what AM requests seems nature to me. Just
like purchasing a car: you won't know the quote until you decided target model(s).
Ok, will check further in these lines and discuss if i have more doubts on it



> 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
>
> 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