[
https://issues.apache.org/jira/browse/FLINK-934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031991#comment-14031991 ]
ASF GitHub Bot commented on FLINK-934:
--------------------------------------
Github user warneke commented on the pull request:
https://github.com/apache/incubator-flink/pull/18#issuecomment-46122924
Using RPCs to distribute jar files is still the quick hack from the very early days of the project. I've already fixed this issue on several branches but I guess the change did not make it to the upstream code. I could offer to take care of this problem, either through some sort of HTTP transfer or by leveraging the distributed file system.
> 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)
Locked
