flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Kunft (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2373) Add configuration parameter to createRemoteEnvironment method
Date Mon, 24 Aug 2015 02:28:45 GMT

    [ https://issues.apache.org/jira/browse/FLINK-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708693#comment-14708693

Andreas Kunft commented on FLINK-2373:

Hey, i was just going to open a PR which had basically also another method for the remote
environment with the extra configuration parameter, just like yours. So I guess, the PR is
now obsolete.
As far as I see it, there is a difference for the configuration provided for the remote environment
and the local one, as the remote config is only used for def. parallelism and the akka config
for the job client and not for configuration of the cluster itself, as the config for the
local execution covers all the configuration.

I think it should be stated clearly in the java doc, that the config is only for the jobclient
and def. parallelism in case of the remote environment. 

> 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

View raw message