[
https://issues.apache.org/jira/browse/FLINK-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345203#comment-14345203
]
ASF GitHub Bot commented on FLINK-999:
--------------------------------------
GitHub user jkirsch opened a pull request:
https://github.com/apache/flink/pull/448
[FLINK-999] Configurability of LocalExecutor
Add also the global configuration to the minicluster.
This is an attempt to bring in the ability to pass configuration parameters
to the embedded mini-cluster - this happened as with more slots, the machine
ran out of network buffers.
The config could then be initialized using for example
`GlobalConfiguration.loadConfiguration("conf");`
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jkirsch/incubator-flink configuration
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/448.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #448
----
commit b37ca76cbfe5b3ede1a130736f4b39d78c980928
Author: Johannes <[email protected]>
Date: 2015-03-03T15:17:47Z
[FLINK-999] Configurability of LocalExecutor
Add also the global configuration to the minicluster
----
> Configurability of LocalExecutor
> --------------------------------
>
> Key: FLINK-999
> URL: https://issues.apache.org/jira/browse/FLINK-999
> Project: Flink
> Issue Type: Wish
> Components: TaskManager
> 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.3.4#6332)
