You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/12/21 19:25:01 UTC
[jira] [Resolved] (IMPALA-6460) More flexible memory-based
admission control policies
[ https://issues.apache.org/jira/browse/IMPALA-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-6460.
-----------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> More flexible memory-based admission control policies
> -----------------------------------------------------
>
> Key: IMPALA-6460
> URL: https://issues.apache.org/jira/browse/IMPALA-6460
> Project: IMPALA
> Issue Type: Epic
> Components: Distributed Exec
> Affects Versions: Impala 2.11.0
> Reporter: Tim Armstrong
> Priority: Major
> Labels: admission-control
> Fix For: Impala 4.0
>
>
> Currently there are only two ways to decided how much memory to reserve for each query in memory-based admission control:
> * Using the memory estimates, which often makes bad decisions (e.g. huge overestimates) and doesn't have any enforcement on the backend
> * Using a static pool or user-set mem_limit, which is very difficult to set to a reasonable value for all queries.
> The memory reservation work will allow us to come up with more powerful and flexible polices
--
This message was sent by Atlassian Jira
(v8.3.4#803005)