[
https://issues.apache.org/jira/browse/FLINK-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531112#comment-16531112
]
ASF GitHub Bot commented on FLINK-9289:
---------------------------------------
GitHub user zentol opened a pull request:
https://github.com/apache/flink/pull/6241
[FLINK-9289][rest] Rework JobSubmitHandler to accept jar files
Backport of #6203 for 1.5.
The differences to the current version of the linked PR (state @
b9a804c350d12469eccf0fd78d82dcac8eaa3c5b) are:
* `ClientUtils` were not introduced
* removed all code related to the upload of artifacts, as this feature was
introduced in 1.6
@tillrohrmann
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zentol/flink 9280_epsilon_bp
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/6241.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 #6241
----
commit a8765ae2f006c99a905afd93e93cbe9b0cfef09b
Author: zentol <chesnay@...>
Date: 2018-06-11T09:45:12Z
[FLINK-9289][rest] Rework JobSubmitHandler to accept jar files
----
> Parallelism of generated operators should have max parallism of input
> ---------------------------------------------------------------------
>
> Key: FLINK-9289
> URL: https://issues.apache.org/jira/browse/FLINK-9289
> Project: Flink
> Issue Type: Bug
> Components: DataSet API
> Affects Versions: 1.5.0, 1.4.2, 1.6.0
> Reporter: Fabian Hueske
> Assignee: Xingcan Cui
> Priority: Major
> Labels: pull-request-available
>
> The DataSet API aims to chain generated operators such as key extraction
> mappers to their predecessor. This is done by assigning the same parallelism
> as the input operator.
> If a generated operator has more than two inputs, the operator cannot be
> chained anymore and the operator is generated with default parallelism. This
> can lead to a {code}NoResourceAvailableException: Not enough free slots
> available to run the job.{code} as reported by a user on the mailing list:
> https://lists.apache.org/thread.html/60a8bffcce54717b6273bf3de0f43f1940fbb711590f4b90cd666c9a@%3Cuser.flink.apache.org%3E
> I suggest to set the parallelism of a generated operator to the max
> parallelism of all of its inputs to fix this problem.
> Until the problem is fixed, a workaround is to set the default parallelism at
> the {{ExecutionEnvironment}}:
> {code}
> ExecutionEnvironment env = ...
> env.setParallelism(2);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
