[
https://issues.apache.org/jira/browse/YARN-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545909#comment-14545909
]
Wangda Tan commented on YARN-3635:
----------------------------------
[~kasha],
Actually no, this patch doesn't do anything to RM when using FS, RMAppManager
use the original user specified queue name to do initialization, and FS can
continue applying QueuePlacementPolicy after app added to scheduler. FS tests
can all get passed also.
Any other thoughts?
> 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: Sub-task
> Components: scheduler
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-3635.1.patch, YARN-3635.2.patch, YARN-3635.3.patch
>
>
> 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)
