[
https://issues.apache.org/jira/browse/FLINK-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716144#comment-14716144
]
ASF GitHub Bot commented on FLINK-2373:
---------------------------------------
GitHub user akunft opened a pull request:
https://github.com/apache/flink/pull/1066
[FLINK-2373] Add configuration parameter to createRemoteEnvironment method
Adds an overloaded ExecutionEnvironment.createRemoteEnvironment method to
provide a custom configuration for the job client. This resolves problems with
the default configuration values, e.g. large jar files causing errors when they
exceeded the default payload size of Akka.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/akunft/flink remoteConf
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1066.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 #1066
----
commit eeabe40e20386b7644c748301d7f9b338a7a2adc
Author: Andreas Kunft <[email protected]>
Date: 2015-07-28T23:58:32Z
[FLINK-2373] Add configuration parameter to createRemoteEnvironment method
----
> Add configuration parameter to createRemoteEnvironment method
> -------------------------------------------------------------
>
> Key: FLINK-2373
> URL: https://issues.apache.org/jira/browse/FLINK-2373
> Project: Flink
> Issue Type: Bug
> Components: other
> Reporter: Andreas Kunft
> Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Currently there is no way to provide a custom configuration upon creation of
> a remote environment (via ExecutionEnvironment.createRemoteEnvironment(...)).
> This leads to errors when the submitted job exceeds the default value for the
> max. payload size in Akka, as we can not increase the configuration value
> (akka.remote.OversizedPayloadException: Discarding oversized payload...)
> Providing an overloaded method with a configuration parameter for the remote
> environment fixes that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
