You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/06/10 17:47:01 UTC

[jira] [Commented] (IMPALA-8536) Add Scalable Pool Configuration to Admission Controller.

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

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

Commit f9cb0a65fe68411e03a57681611cbcc87dfaaf50 in impala's branch refs/heads/master from Bikramjeet Vig
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=f9cb0a6 ]

IMPALA-9077: Remove scalable admission control configs

Removed the 3 scalable configs added in IMPALA-8536:
- Max Memory Multiple
- Max Running Queries Multiple
- Max Queued Queries Multiple

This patch removes the functionality related to those configs but
retains the additional test coverage and cleanup added in
IMPALA-8536. This removal is to make it easier to enhance
Admission Control using Executor Groups which has turned out to
be a useful building block.

Testing:
Ran core tests.

Change-Id: Ib9bd63f03758a6c4eebb99c64ee67e60cb56b5ac
Reviewed-on: http://gerrit.cloudera.org:8080/16039
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>


> Add Scalable Pool Configuration to Admission Controller.
> --------------------------------------------------------
>
>                 Key: IMPALA-8536
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8536
>             Project: IMPALA
>          Issue Type: New Feature
>          Components: Backend
>    Affects Versions: Impala 3.2.0
>            Reporter: Andrew Sherman
>            Assignee: Andrew Sherman
>            Priority: Major
>              Labels: admission-control, resource-management, scalability
>
> Add configuration parameters to Admission Controller that scale with
> the number of hosts in the resource pool. The planned parameters are
> * Max Running Queries Multiple - the Multiple of the current total number of running Impalads which gives the maximum number of concurrently running queries in this pool. 
> * Max Queued Queries Multiple - the Multiple of the current total number of running Impalads which gives the maximum number of queries that can be queued in this pool. 
> * Max Memory Multiple - the Multiple of the current total number of running Impalads which gives the maximum memory available across the cluster for the pool.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org