[
https://issues.apache.org/jira/browse/IMPALA-9077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750850#comment-17750850
]
ASF subversion and git services commented on IMPALA-9077:
---------------------------------------------------------
Commit a24897269d35c1ec012709c4d515aac687243124 in impala's branch
refs/heads/master from Andrew Sherman
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=a24897269 ]
IMPALA-12332: Undo IMPALA-8615 as the corresponding configs have been removed
IMPALA-8615 documented the changes made in IMPALA-8536, but the configs
were subsequently removed in IMPALA-9077. Rollback IMPALA-8615 to bring
the docs up to date.
Revert "IMPALA-8615: [DOCS] Document the scalable admission control parameters"
This was a clean revert, and there were no overlapping changes to this file.
TESTING:
- built docs and reviewed the file.
This reverts commit b2136c39fcafacec308dc9dd13ad13133596d05d.
Change-Id: Ibc856c62babb4b305b6a7c286a0f4c86e6e418cc
Reviewed-on: http://gerrit.cloudera.org:8080/20308
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
