[
https://issues.apache.org/jira/browse/IMPALA-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Jacobs resolved IMPALA-5644.
------------------------------------
Resolution: Fixed
Fix Version/s: Impala 2.10.0
https://github.com/apache/incubator-impala/commit/7264c547516569b6c1152bcb61724ee8c2ee79d0
> Fail queries early when their minimum reservation is too high to execute
> within the given mem_limit
> ---------------------------------------------------------------------------------------------------
>
> Key: IMPALA-5644
> URL: https://issues.apache.org/jira/browse/IMPALA-5644
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 2.10.0
> Reporter: Tim Armstrong
> Assignee: Matthew Jacobs
> Fix For: Impala 2.10.0
>
>
> With the initial version of IMPALA-3200, we won't check whether the minimum
> reservation fits within the query memory limit until fragment startup time.
> There are a couple of decisions to make here:
> * How to deal with the RESERVATION_MEM_FRACTION/RESERVATION_MEM_MIN_REMAINING
> heuristic that limits reservation relative to the query mem_limit
> * Where to actually reject the query
> This is a bit tricky since it needs to happen after we've determined the
> applicable memory limit (which depends on resolving the request pool).
> Admission control would be one place but admission control can be disabled.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
