[ 
https://issues.apache.org/jira/browse/IMPALA-12264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904850#comment-17904850
 ] 

ASF subversion and git services commented on IMPALA-12264:
----------------------------------------------------------

Commit 2280c1362ebdc9f9827e1928e7b3a822b1533302 in impala's branch 
refs/heads/master from Andrew Sherman
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=2280c1362 ]

IMPALA-12943: Document Admission Control User Quotas.

Document the feature introduced in IMPALA-12345. Add a few more tests to
the QuotaExamples test which demonstrate the examples used in the
docs.

Clarify in docs and code the behavior when a user is a member of more
than one group for which there are rules. In this case the least
restrictive rule applies.

Also document the '--max_hs2_sessions_per_user' flag introduced in
IMPALA-12264.

Change-Id: I82e044adb072a463a1e4f74da71c8d7d48292970
Reviewed-on: http://gerrit.cloudera.org:8080/22100
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Add configuration to limit concurrent connections
> -------------------------------------------------
>
>                 Key: IMPALA-12264
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12264
>             Project: IMPALA
>          Issue Type: New Feature
>          Components: Backend
>            Reporter: Quanlong Huang
>            Assignee: Andrew Sherman
>            Priority: Major
>             Fix For: Impala 4.4.0
>
>
> To prevent a rogue application from repeatedly connecting to and monopolizing 
> Impala, we can add configurations to limit concurrent connections. E.g. limit 
> the number of concurrent connections per user, IP address, or the user and IP 
> address combination.
> CC [[email protected]] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to