[
https://issues.apache.org/jira/browse/HIVE-10725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-10725:
------------------------------------
Description:
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.
5. See if we can recommend reasonable values for OS resources or provide alerts
if we run out of those.
6. Health reports, server status API (to get number of queries, sessions etc).
was:
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.
> 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.
> 5. See if we can recommend reasonable values for OS resources or provide
> alerts if we run out of those.
> 6. Health reports, server status API (to get number of queries, sessions etc).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
