hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vaibhav Gumashta (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HIVE-14847) HiveServer2: Implement some admission control mechanism for graceful degradation when resources are exhausted
Date Tue, 27 Sep 2016 16:01:20 GMT
Vaibhav Gumashta created HIVE-14847:
---------------------------------------

             Summary: HiveServer2: Implement some admission control mechanism for graceful
degradation when resources are exhausted
                 Key: HIVE-14847
                 URL: https://issues.apache.org/jira/browse/HIVE-14847
             Project: Hive
          Issue Type: Bug
          Components: HiveServer2
    Affects Versions: 0.12.0, 0.13.0, 0.14.0, 0.15.0
            Reporter: Vaibhav Gumashta
            Assignee: Peter Vary


An example of where it is needed: 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). Similarly, we should also review
the behaviour of background thread pool to have a well defined behavior on the the pool getting
exhausted. 

Ideally implementing some form of general admission control will be a better solution, so
that we do not accept new work unless sufficient resources are available and display graceful
degradation under overload.



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

Mime
View raw message