You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2019/04/26 06:24:00 UTC

[jira] [Resolved] (IMPALA-8119) Improve experience for configuring JVM heap size in docker container.

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

Tim Armstrong resolved IMPALA-8119.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.3.0

> Improve experience for configuring JVM heap size in docker container.
> ---------------------------------------------------------------------
>
>                 Key: IMPALA-8119
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8119
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Infrastructure
>    Affects Versions: Impala 3.2.0
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Major
>              Labels: docker
>             Fix For: Impala 3.3.0
>
>
> The heap size can be configured via JAVA_TOOL_OPTIONS. Configuring the JVM heap size is likely a common task when deploying Impala containers to production because the catalogd and coordinators need to be sized to fit the working set of metadata - it would be worthwhile to have a more explicit and clearly-documented way to set the heap size.
> We could also try to be fancy and choose a heap size based on the container memory limit and the role of the container.



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