[jira] [Commented] (FLINK-934) Job and TaskManager startup scripts always set JVM heap size

Posted by Shang Yuanchun (Jira) on Jun 17, 2014; 12:54pm
URL: http://deprecated-apache-flink-mailing-list-archive.368.s1.nabble.com/jira-Commented-FLINK-934-Job-and-TaskManager-startup-scripts-always-set-JVM-heap-size-tp332.html


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

Stephan Ewen commented on FLINK-934:
------------------------------------

The previous "was merged" message was wrong. Confusion with a similar issue.

> 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
(v6.2#6252)