Vinod Kumar Vavilapalli commented on YARN-2257:

Some part of this is a core YARN feature and shouldn't be built for each 
scheduler - the part about maintaining a user-queue mappings and then accepting 
submissions from users automatically to those queues. The configuration can be 
per scheduler.

I propose we fix it in general. Will edit the subject if there is no 

> Add user to queue mapping in Fair-Scheduler
> -------------------------------------------
>                 Key: YARN-2257
>                 URL: https://issues.apache.org/jira/browse/YARN-2257
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: scheduler
>            Reporter: Patrick Liu
>              Labels: features
> Currently, the fair-scheduler supports two modes, default queue or individual 
> queue for each user.
> Apparently, the default queue is not a good option, because the resources 
> cannot be managed for each user or group.
> However, individual queue for each user is not good enough. Especially when 
> connecting yarn with hive. There will be increasing hive users in a corporate 
> environment. If we create a queue for a user, the resource management will be 
> hard to maintain.
> I think the problem can be solved like this:
> 1. Define user->queue mapping in Fair-Scheduler.xml. Inside each queue, use 
> aclSubmitApps to control user's ability.
> 2. Each time a user submit an app to yarn, if the user has mapped to a queue, 
> the app will be scheduled to that queue; otherwise, the app will be submitted 
> to default queue.
> 3. If the user cannot pass aclSubmitApps limits, the app will not be accepted.

This message was sent by Atlassian JIRA

Reply via email to