[
https://issues.apache.org/jira/browse/FLINK-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720217#comment-14720217
]
ASF GitHub Bot commented on FLINK-2373:
---------------------------------------
Github user akunft commented on the pull request:
https://github.com/apache/flink/pull/1066#issuecomment-135830165
After thinking about it, I would change the behavior so that the config is
only for defining akka specific settings. The default parallelism of the
operators can be set via ```setParallelism```, just like in the local
environment. Otherwise, we had to use ```parallelism.default``` to set the
operators parallelism, which is confusing imo. This also goes in line with the
configuration description on the website.
What do you think?
In any case, I will create unit tests and update the PR once we decided on
a version.
> 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)
