hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-314) Schedulers should allow resource requests of different sizes at the same priority and location
Date Wed, 20 May 2015 20:05:02 GMT

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

Karthik Kambatla commented on YARN-314:
---------------------------------------

I am essentially proposing an efficient way to index the pending requests across multiple
axes. Each of these indices are captured by a map. The only reason to colocate them is to
not disperse this indexing (mapping) logic across multiple classes. 

We should able to quickly look up all requests for an app for reporting etc., and also look
up all node-local requests across applications at schedule time without having to iterate
through all the applications. 

The maps could be - <App, <Priority, <Locality, ResourceRequest>>>, <Locality
(node/rack), <Priority, <App, ResourceRequest>>>. Current {{AppSchedulingInfo}}
could stay as is and use the former map to get the corresponding requests.

> Schedulers should allow resource requests of different sizes at the same priority and
location
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-314
>                 URL: https://issues.apache.org/jira/browse/YARN-314
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: scheduler
>    Affects Versions: 2.0.2-alpha
>            Reporter: Sandy Ryza
>         Attachments: yarn-314-prelim.patch
>
>
> Currently, resource requests for the same container and locality are expected to all
be the same size.
> While it it doesn't look like it's needed for apps currently, and can be circumvented
by specifying different priorities if absolutely necessary, it seems to me that the ability
to request containers with different resource requirements at the same priority level should
be there for the future and for completeness sake.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message