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 "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/07/25 22:40:00 UTC

[jira] [Updated] (IMPALA-7349) Automatically choose mem_limit based on estimate, clamped to range

     [ https://issues.apache.org/jira/browse/IMPALA-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong updated IMPALA-7349:
----------------------------------
    Issue Type: Improvement  (was: Sub-task)
        Parent:     (was: IMPALA-6460)

> Automatically choose mem_limit based on estimate, clamped to range
> ------------------------------------------------------------------
>
>                 Key: IMPALA-7349
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7349
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Tim Armstrong
>            Assignee: Bikramjeet Vig
>            Priority: Major
>              Labels: admission-control, resource-management
>
> We should add admission control support for intelligently choosing how much memory to give a query, based on the memory estimate. Currently we require that you set a single mem_limit per pool. Instead it would be better if we allowed configuring min/max guardrails within which admission control chose an amount of memory that will allow good performance.
> Initially, I think mem_limit will be the same for all backends. Eventually it could make sense to have different limits per backend depending on the fragments.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org