flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-934) Job and TaskManager startup scripts always set JVM heap size
Date Fri, 13 Jun 2014 14:40:01 GMT

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

Stephan Ewen resolved FLINK-934.

       Resolution: Fixed
    Fix Version/s: 0.6-incubating
         Assignee: Ufuk Celebi

Solved in commit 79acf26d0d866a9eafb76d14a3579f336c4cc2f7

> Job and TaskManager startup scripts always set JVM heap size
> ------------------------------------------------------------
>                 Key: FLINK-934
>                 URL: https://issues.apache.org/jira/browse/FLINK-934
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>             Fix For: 0.6-incubating
> The default distribution config {{stratosphere-conf.yaml}} contains keys {{jobmanager.heap.mb}}
and {{taskmanager.heap.mb}} for the heap sizes of the JobManager and TaskManager JVMs. If
they are not set, {{config.sh}} has default values for them.
> We _always_ use one of these values and set the {{Xms}} and {{Xmx}} properties. After
a short discussion with [~rmetzger] and [~StephanEwen] we actually expected that they should
not be set if not found in {{stratosphere-conf.yaml}}. This would result in a fall back to
the respective JVM default (imho 1/4th of the physical memory since Java 6).

This message was sent by Atlassian JIRA

View raw message