hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ram Venkatesh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5520) [Capacity Scheduler] Change the logic for when to trigger user/group mappings to queues
Date Sat, 13 Aug 2016 23:56:22 GMT

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

Ram Venkatesh commented on YARN-5520:
-------------------------------------

[~mshen] thank you for creating this issue to enhance the queue mapping functionality.

Re. there's no way to fully disable queue overriding when mappings are configured inside capacity-scheduler.xml
- 

There are three items to be considered here:
1. What to do if the user specified did not specify a queue (IIRC in the original implementation
this was indistinguishable from the user specifying YarnConfiguration.DEFAULT_QUEUE_NAME)

2. The user specified a queue but the admin wants to override it with what they deem is the
right queue for the job. This is what yarn.scheduler.capacity.queue-mappings-override.enable
was supposed to control
3. the use case that you are pointing out where your users want to submit to the "adhoc" queue,
overriding the mapping that the admin has in place.

Can you please describe how you plan to handle the policy choices for (2) and (3)?

thanks!
ram

> [Capacity Scheduler] Change the logic for when to trigger user/group mappings to queues
> ---------------------------------------------------------------------------------------
>
>                 Key: YARN-5520
>                 URL: https://issues.apache.org/jira/browse/YARN-5520
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 2.6.0, 2.7.0, 2.6.1
>            Reporter: Min Shen
>
> In YARN-2411, the feature in Capacity Scheduler to support user/group based mappings
to queues was introduced.
> In the original implementation, the configuration key {{yarn.scheduler.capacity.queue-mappings-override.enable}}
was added to control when to enable overriding user requested queues.
> However, even if this configuration is set to false, queue overriding could still happen
if the user didn't request for any specific queue or choose to simply submit his job to "default"
queue, according to the following if condition which triggers queue overriding:
> {code}
> if (queueName.equals(YarnConfiguration.DEFAULT_QUEUE_NAME)
>               || overrideWithQueueMappings)
> {code}
> This logic does not seem very reasonable, as there's no way to fully disable queue overriding
when mappings are configured inside capacity-scheduler.xml.
> In addition, in our environment, we have setup a few organization dedicated queues as
well as some "adhoc" queues. The organization dedicated queues have better resource guarantees
and we want to be able to route users to the corresponding organization queues. On the other
hand, the "adhoc" queues have less resource guarantees but everyone can use it to get some
opportunistic resources when the cluster is free.
> The current logic will also prevent this type of use cases as when you enable queue overriding,
users cannot use these "adhoc" queues any more. They will always be routed to the dedicated
organization queues.
> To address the above 2 issues, I propose to change the implementation so that:
> * Admin can fully disable queue overriding even if mappings are already configured.
> * Admin have finer grained control to cope queue overriding with the above mentioned
organization/adhoc queue setups.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message