[jira] [Resolved] (IMPALA-7389) Admission control should set aside less memory on dedicated coordinator if coordinator fragment is lightweight

["Tim Armstrong (Jira)" <ji...@apache.org>]

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

Tim Armstrong resolved IMPALA-7389.
-----------------------------------
    Resolution: Duplicate

I guess I filed two version of this - IMPALA-7486

> Admission control should set aside less memory on dedicated coordinator if coordinator fragment is lightweight
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-7389
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7389
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Distributed Exec
>    Affects Versions: Impala 3.0, Impala 2.12.0
>            Reporter: Tim Armstrong
>            Priority: Major
>              Labels: admission-control, resource-management
>
> The current admission control treats all backends symmetrically and sets aside the mem_limit. This makes sense for now given that we have the same mem_limit setting for all backends. 
> One case where this could be somewhat problematic is if you have dedicated coordinators with less memory than the executors, because the coordinator's process memory limit will be fully admitted before the executors.
> If you have multiple coordinators and queries are distributed between them this is relatively unlikely to become a problem. If you have a single coordinator this is more of an issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)