[
https://issues.apache.org/jira/browse/FLINK-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051267#comment-14051267
]
Ufuk Celebi commented on FLINK-999:
-----------------------------------
+1
> Configurability of LocalExecutor
> --------------------------------
>
> Key: FLINK-999
> URL: https://issues.apache.org/jira/browse/FLINK-999
> Project: Flink
> Issue Type: Wish
> Reporter: Till Rohrmann
> Priority: Minor
>
> I noticed when running locally some examples with the Scala API that the
> TaskManagers ran out of network buffers when increasing the number of slots
> on one machine. Trying to adjust the value, I stumbled across a more
> naturally grown interface in LocalExecutor and NepheleMiniCluster. Some
> parameters are specified as attributes of NepheleMiniCluster, others are
> loaded from a configuration file and others use the default value specified
> in ConfigConstants. I think it would be good to give the user the ability to
> easily control the different parameters in a unified fashion by providing a
> configuration object. Furthermore, the NepheleMiniCluster is not consistent
> with the use of parameter values: For example, getJobClient sets the
> jobmanager rpc port with respect to the attribute jobManagerRpcPort whereas
> the start method can retrieve it from a specified configuration file.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
