hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pengcheng Xiong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-13158) HiveServer should pick AMs which are already ready from the pool
Date Sat, 25 Mar 2017 20:19:42 GMT

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

Pengcheng Xiong commented on HIVE-13158:
----------------------------------------

I am deferring this to Hive 3.0 as we are going to cut the first RC and it is not marked as
blocker. Please feel free to commit to the branch if this can be resolved before the release.

> 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.15#6346)

Mime
View raw message