[
https://issues.apache.org/jira/browse/HIVE-12938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HIVE-12938:
------------------------------------
Description:
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, 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.
was:
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.
> 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, 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)
