You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2016/05/25 16:25:12 UTC

[jira] [Updated] (HIVE-13158) HiveServer should pick AMs which are already ready from the pool

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

Jesus Camacho Rodriguez updated HIVE-13158:
-------------------------------------------
    Target Version/s: 2.2.0  (was: 2.1.0)

> HiveServer should pick AMs which are already ready from the pool
> ----------------------------------------------------------------
>
>                 Key: HIVE-13158
>                 URL: https://issues.apache.org/jira/browse/HIVE-13158
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Siddharth Seth
>
> Scenario. Start HiveServer2 with 3 sessions. At startup there's capacity for this.
> All 3 sessions time out.
> There's capacity for one session only.
> The first query submitted will start a session and use it.
> The second query submitted (after the first one is submitted) ends up trying to launch a new session as well - instead of using the existing free session. Since there's no capacity, this ends up blocking.



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