hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2257) Add user to queue mappings to automatically place users' apps into specific queues
Date Wed, 16 Jul 2014 17:02:05 GMT

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

Wangda Tan commented on YARN-2257:
----------------------------------

Hi [~sandyr],
Thanks for pointing me this,
I have a question here, what's the expected behavior when an admin what's to add a new QueuePlacementRule?
I guess a new class need to be added to Hadoop project, and need rebuild Hadoop, right?
I think it's a little over-kill here, user may want convenient instead of flexibility. If
you think the rules I mentioned is not flexible enough, maybe we can extend it to rules with
pattern, like %user->root.users.%user which means putting application from %user to root.users.%user.
Which maybe easier for admin to add new QueuePlacementRule.
I agree it's a good fit for YARN in general, but we should make it easier to use. 

Please feel free to let me know you comments, thanks.
Wangda

> Add user to queue mappings to automatically place users' apps into specific queues
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-2257
>                 URL: https://issues.apache.org/jira/browse/YARN-2257
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: scheduler
>            Reporter: Patrick Liu
>            Assignee: Vinod Kumar Vavilapalli
>              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
(v6.2#6252)

Mime
View raw message