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 "Zoltán Borók-Nagy (Jira)" <ji...@apache.org> on 2026/03/20 13:00:00 UTC
[jira] [Assigned] (IMPALA-14840) Pool can use more memory than Max Memory when Min/Max Query Memory limit is not set
[ https://issues.apache.org/jira/browse/IMPALA-14840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zoltán Borók-Nagy reassigned IMPALA-14840:
------------------------------------------
Assignee: Zoltán Borók-Nagy
> Pool can use more memory than Max Memory when Min/Max Query Memory limit is not set
> -----------------------------------------------------------------------------------
>
> Key: IMPALA-14840
> URL: https://issues.apache.org/jira/browse/IMPALA-14840
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Zoltán Borók-Nagy
> Assignee: Zoltán Borók-Nagy
> Priority: Major
>
> Based on the following comments a query can use unlimited resources if
> * Pool has no Min and Max Query Memory LImit
> * Query option MEM_LIMIT is not set
> https://github.com/apache/impala/blob/787b63a4b88b91bf441200e336ca0bac873541b9/be/src/scheduling/schedule-state.cc#L301-L303
> {noformat}
> // If the min_query_mem_limit and max_query_mem_limit are not set in the pool config
> // then it falls back to traditional(old) behavior, which means that, it sets the
> // mem_limit if it is set in the query options, else sets it to -1 (no limit).
> {noformat}
> https://github.com/apache/impala/blob/787b63a4b88b91bf441200e336ca0bac873541b9/be/src/scheduling/schedule-state.cc#L411
> This can lead to using more memory than the specified "Max Memory" for the pool.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org