[
https://issues.apache.org/jira/browse/HIVE-10725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546118#comment-14546118
]
Vaibhav Gumashta commented on HIVE-10725:
-----------------------------------------
cc [~thejas] [~alangates] [~rbains].
Please add any ideas you may have on this. The end goal is to prevent HS2 from
becoming unresponsive/going OOM.
> 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)
