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

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

Discussed this with [~asuresh] offline. We were wondering if AppSchedulingInfo 
should be supplemented (or replaced) by another singleton data structure that 
captures pending requests and maintains multiple maps - to index these requests 
by both apps and nodes/racks. We should of course add other convenience methods 
to add/remove or query these 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)

Reply via email to