[
https://issues.apache.org/jira/browse/HIVE-19005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411358#comment-16411358
]
BELUGA BEHR commented on HIVE-19005:
------------------------------------
[~asherman] Thanks for working with me on this.
There is not enough documentation to understand the changes introduced in
[HIVE-16917], but it is not that helpful if it's blocking on the connecting
user and not the proxy user. As I said, the 'hue' user will have many
connections, but then Hue must add logic to control its individual user
connections. But in a mixed environment, with Hue and beeline, then we would
want to cap the per-user connections to "5" perhaps, but that will cause
trouble for Hue which may be supporting many simultaneous users.
Also, this is a per-server configuration. It would be better if user /
session-id tupples were stored in ZK and this limit was applied across all HS2
instances in the environment.
> Maximum Session Per User
> ------------------------
>
> Key: HIVE-19005
> URL: https://issues.apache.org/jira/browse/HIVE-19005
> Project: Hive
> Issue Type: New Feature
> Components: HiveServer2
> Affects Versions: 3.0.0, 2.4.0, 2.3.2
> Reporter: BELUGA BEHR
> Priority: Minor
>
> # Set a maximum number of connections/sessions per user (keeping in mind
> proxy users)
> # Set a maximum number of sessions globally
> Would need to track active sessions in ZK or DB.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
