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 2019/01/29 09:58:00 UTC

[jira] [Resolved] (IMPALA-7940) Automatically set process memory limit to a good value when running in a container

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

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

IMPALA-7941 changed the default for containers

> Automatically set process memory limit to a good value when running in a container
> ----------------------------------------------------------------------------------
>
>                 Key: IMPALA-7940
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7940
>             Project: IMPALA
>          Issue Type: Epic
>          Components: Backend
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Major
>              Labels: admission-control, resource-management
>
> It would be convenient if, when starting up an Impala daemon in a container, it could automatically configure its own memory limit to the right value so that queries won't be overadmitted. It should sniff out the memory limit for the container (if there is one set).
> E.g. see what Java did https://www.opsian.com/blog/java-on-docker/



--
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