hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-8424) Support fair scheduler user queue mapping in non-impersonation mode
Date Sun, 12 Oct 2014 08:35:34 GMT

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

Lefty Leverenz commented on HIVE-8424:
--------------------------------------

After a little reading about the YARN fair scheduler I'm quite confused.  I'll revisit this
later, but here are my first questions:

When *hive.server2.map.fair.scheduler.queue* is true, how are users mapped to queues -- is
that a YARN configuration instead of Hive, or is it automatic?

When *hive.server2.map.fair.scheduler.queue* is false, does every job go on the same queue
(as 'hive' user) or does each job get a separate queue, or something else?  This jira's description
says "The default scheduler queue mapping is one queue per user" -- does that correspond to
*hive.server2.map.fair.scheduler.queue* being false?


> Support fair scheduler user queue mapping in non-impersonation mode
> -------------------------------------------------------------------
>
>                 Key: HIVE-8424
>                 URL: https://issues.apache.org/jira/browse/HIVE-8424
>             Project: Hive
>          Issue Type: Improvement
>          Components: Shims
>            Reporter: Mohit Sabharwal
>            Assignee: Mohit Sabharwal
>         Attachments: HIVE-8424.1.patch, HIVE-8424.patch
>
>
> Under non-impersonation mode, all MR jobs run as the hive system user. The default scheduler
queue mapping is one queue per user. This is problematic for users who use the queues to regulate
and track their MR resource usage.
> Yarn exposes an API to retrieve the fair scheduler queue mapping, which we can use to
set the appropriate MR queue for the current user.



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

Mime
View raw message