You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2016/01/27 00:47:40 UTC

[jira] [Updated] (HIVE-12938) Tez session pool shouldn't create a new session if one of the default queues is specified

     [ https://issues.apache.org/jira/browse/HIVE-12938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Shelukhin updated HIVE-12938:
------------------------------------
    Issue Type: Improvement  (was: Bug)

> Tez session pool shouldn't create a new session if one of the default queues is specified
> -----------------------------------------------------------------------------------------
>
>                 Key: HIVE-12938
>                 URL: https://issues.apache.org/jira/browse/HIVE-12938
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Takahiko Saito
>
> Presenlty, Tez session pool says "if the user has specified a queue name themselves, we create a new session". Which is what it actually does. This can lead to a counter-intuitive situation where we have idle pool sessions for a queue foo, the user requests a session from that queue, and a new one is started.
> It should be possible to choose a pool session if it's from one of the default queues... we need to see if it's reasonable to have a separate lookup structure for that. As luck would have it, there's already some in-use state tracking on the sessions themselves.



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