hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <>
Subject [jira] [Commented] (HIVE-16917) HiveServer2 guard rails - Limit concurrent connections from user
Date Wed, 01 Nov 2017 18:25:00 GMT


Prasanth Jayachandran commented on HIVE-16917:

[~asherman] Yes. Single connection can be used to execute queries in a loop which can potentially
max out number of worker threads leading to denial-of-service/rejections for other users.
Since we have session handle even when we execute query I think it should be easy to extend
(in a subsequent or followup jira?) this to add guardrails for limiting queries per user/ip-address
as well. The usecase for this jira was to avoid creating too many connections (and not closing
it), which will increase the memory pressure of HS2 (long GC pauses) eventually leading to
unusable state. This doesn't do the cleanup of stale connections but atleast will enforce
some limits (instead of infinite connections).

> HiveServer2 guard rails - Limit concurrent connections from user
> ----------------------------------------------------------------
>                 Key: HIVE-16917
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: HiveServer2
>            Reporter: Thejas M Nair
>            Assignee: Prasanth Jayachandran
>            Priority: Major
>         Attachments: HIVE-16917.1.patch
> Rogue applications can make HS2 unusable for others by making too many connections at
a time.
> HS2 should start rejecting the number of connections from a user, after it has reached
a configurable threshold.

This message was sent by Atlassian JIRA

View raw message