impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Armstrong (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IMPALA-5644) Fail queries early when their minimum reservation is too high to execute within the given mem_limit
Date Mon, 10 Jul 2017 23:48:00 GMT
Tim Armstrong created IMPALA-5644:
-------------------------------------

             Summary: 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: Tim Armstrong


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)

Mime
View raw message