[
https://issues.apache.org/jira/browse/FLINK-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716294#comment-14716294
]
ASF GitHub Bot commented on FLINK-2373:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/1066#discussion_r38074069
--- Diff:
flink-java/src/main/java/org/apache/flink/api/java/ExecutionEnvironment.java ---
@@ -1105,6 +1105,27 @@ public static ExecutionEnvironment
createRemoteEnvironment(String host, int port
}
/**
+ * Creates a {@link RemoteEnvironment}. The remote environment sends
(parts of) the program
+ * to a cluster for execution. Note that all file paths used in the
program must be accessible from the
+ * cluster. The custom configuration file is used to configure the
default parallelism and Akka specific
+ * configuration parameters for the JobClient only. Cluster
configuration has to be done in the remotely
+ * running Flink instance.
--- End diff --
Very good :-)
> 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)
