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

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

    [ https://issues.apache.org/jira/browse/IMPALA-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826260#comment-16826260 ] 

Tim Armstrong commented on IMPALA-8119:
---------------------------------------

We currently have this code in daemon_entrypoint.sh:
{code}
# Default to 2GB heap. Allow overriding by externally-set JAVA_TOOL_OPTIONS.
export JAVA_TOOL_OPTIONS="-Xmx2g $JAVA_TOOL_OPTIONS"
{code}

I looked at different helm charts to see if there's a de-facto standard for how to do this, but it's varied - some use env vars and some put the args into a file in a directory that gets picked up by a wrapper.

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

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