[
https://issues.apache.org/jira/browse/HIVE-9423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-9423:
-----------------------------------
Summary: HiveServer2: Implement some admission control policy (was:
HiveServer2: handle max handler thread exhaustion gracefully)
> HiveServer2: Implement some admission control policy
> ----------------------------------------------------
>
> Key: HIVE-9423
> URL: https://issues.apache.org/jira/browse/HIVE-9423
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 0.12.0, 0.13.0, 0.14.0, 0.15.0
> Reporter: Vaibhav Gumashta
>
> It has been reported that when # of client connections is greater than
> {{hive.server2.thrift.max.worker.threads}}, HiveServer2 stops accepting new
> connections and ends up having to be restarted. This should be handled more
> gracefully by the server and the JDBC driver, so that the end user gets aware
> of the problem and can take appropriate steps (either close existing
> connections or bump of the config value or use multiple server instances with
> dynamic service discovery enabled).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
