You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2015/08/13 11:57:46 UTC
[jira] [Commented] (FLINK-2373) Add configuration parameter to
createRemoteEnvironment method
[ https://issues.apache.org/jira/browse/FLINK-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694989#comment-14694989 ]
Ufuk Celebi commented on FLINK-2373:
------------------------------------
Andreas, did you have a look at this? I have a small change as part of an upcoming pull request to allow this as well. I will keep it simple and just add:
{code}
createRemoteEnvironment(Configuration flinkConfig, String... jarFiles)
{code}
It would be nice to think about the "whole" execution environment stack and have it more consistent.
> 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)