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

Vinod Kumar Vavilapalli commented on YARN-3635:
-----------------------------------------------

+10 for this.

In addition to the interfaces themselves, I'd like us to consolidate the 
concrete mapping-rules that we have in each scheduler. Ideally, we only need 
one set of rules acceptable by all schedulers. If not that, I'd live with ~80% 
common rules.

BTW, thematically this fits into YARN-1317, making it a sub-task.

> Get-queue-mapping should be a common interface of YarnScheduler
> ---------------------------------------------------------------
>
>                 Key: YARN-3635
>                 URL: https://issues.apache.org/jira/browse/YARN-3635
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>
> Currently, both of fair/capacity scheduler support queue mapping, which makes 
> scheduler can change queue of an application after submitted to scheduler.
> One issue of doing this in specific scheduler is: If the queue after mapping 
> has different maximum_allocation/default-node-label-expression of the 
> original queue, {{validateAndCreateResourceRequest}} in RMAppManager checks 
> the wrong queue.
> I propose to make the queue mapping as a common interface of scheduler, and 
> RMAppManager set the queue after mapping before doing validations.



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

Reply via email to