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:00 UTC
[jira] [Commented] (IMPALA-9077) Fix scalable admission config for
clusters with dedicated coordinators
[ https://issues.apache.org/jira/browse/IMPALA-9077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132553#comment-17132553 ]
ASF subversion and git services commented on IMPALA-9077:
---------------------------------------------------------
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>
> Fix scalable admission config for clusters with dedicated coordinators
> ----------------------------------------------------------------------
>
> Key: IMPALA-9077
> URL: https://issues.apache.org/jira/browse/IMPALA-9077
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 3.3.0
> Reporter: Bikramjeet Vig
> Assignee: Bikramjeet Vig
> Priority: Major
>
> The scalable configs are:
> Max Memory Multiple
> Max Running Queries Multiple
> Max Queued Queries Multiple
> Currently the scalable configs scale based on number of total executors. This can work for max running or queued queries multiple, but for "Max Memory Multiple" this will cause the following problem:
> Consider the following cluster composed of 2 dedicated coordinators and 2 executors. For a regular query that will run on 2 executors and 1 coordinator, if the memory to admit per backend is 100MB, the cluster memory to be admitted will be 300MB. Now if the max_memory_multiple is 120MB this query will not be admitted because the scalable max memory will be 120*2 = 240.
--
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