hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-10725) Better resource management in HiveServer2
Date Fri, 15 May 2015 22:04:01 GMT

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

Thejas M Nair commented on HIVE-10725:
--------------------------------------

I think it will also be useful examine a way to provide detailed health reports that can be
consumed by monitoring tools.

Also with dynamic service discovery now available, we should also look at the option of making
an auto-restart feature available . It should be possible to enable this using a config. cc
[~apivovarov]


> Better resource management in HiveServer2
> -----------------------------------------
>
>                 Key: HIVE-10725
>                 URL: https://issues.apache.org/jira/browse/HIVE-10725
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2, JDBC
>    Affects Versions: 1.3.0
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>
> We have various ways to control the number of queries that can be run on one HS2 instance
(max threads, thread pool queuing etc). We also have ways to run multiple HS2 instances using
dynamic service discovery. We should do a better job at:
> 1. Monitoring resource utilization (sessions, ophandles, memory, threads etc).
> 2. Being upfront to the client when we cannot accept new queries.
> 3. Throttle among different server instances in case dynamic service discovery is used.
> 4. Consolidate existing ways to control #queries into a simpler model.



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

Mime
View raw message