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 "Alex Rodoni (JIRA)" <ji...@apache.org> on 2019/06/03 20:32:00 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=16855017#comment-16855017 ]
Alex Rodoni commented on IMPALA-8536:
-------------------------------------
[~asherman] What is the target version for this?
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org