[
https://issues.apache.org/jira/browse/FLINK-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654488#comment-15654488
]
ASF GitHub Bot commented on FLINK-5040:
---------------------------------------
GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/2784
[backport] [FLINK-5040] [jobmanager] Set correct input channel types with
eager scheduling
Backport of #2783 with no major differences.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uce/flink eager_deployment-backport_1.1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2784.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 #2784
----
commit 2790511f6cf261537da6b3f909add29092c613d0
Author: Ufuk Celebi <u...@apache.org>
Date: 2016-11-10T13:01:22Z
Revert "[FLINK-3232] [runtime] Add option to eagerly deploy channels"
The reverted commit did not really fix anything, but hid the problem by
brute force, sending many more schedule or update consumers messages.
commit 10ffceea52b168a4819b41efb85a04a98ede0078
Author: Ufuk Celebi <u...@apache.org>
Date: 2016-11-10T16:25:06Z
Revert "[FLINK-3232] [runtime] Add option to eagerly deploy channels"
The reverted commit did not really fix anything, but hid the problem by
brute force, sending many more schedule or update consumers messages.
commit 097c4eae2931dc8c11d8fda28a36b715f5f376a6
Author: Ufuk Celebi <u...@apache.org>
Date: 2016-11-09T17:25:06Z
[FLINK-5040] [jobmanager] Set correct input channel types with eager
scheduling
commit b549789956d4d1e594f2bfb642137e1f3f074b9c
Author: Ufuk Celebi <u...@apache.org>
Date: 2016-11-10T10:15:47Z
[FLINK-5040] [taskmanager] Adjust partition request backoffs
The back offs were hard coded before, which would have made it
impossible to react to any potential problems with them.
----
> Set correct input channel types with eager scheduling
> -----------------------------------------------------
>
> Key: FLINK-5040
> URL: https://issues.apache.org/jira/browse/FLINK-5040
> Project: Flink
> Issue Type: Bug
> Components: JobManager
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
> Fix For: 1.2.0, 1.1.4
>
>
> When we do eager deployment all intermediate stream/partition locations are
> already known when scheduling an intermediate stream/partition consumer.
> Nonetheless we saw tasks with "unknown input channels" that were updated
> lazily during runtime. This was caused by a wrong producer execution state
> check requiring the producers to be in RUNNING or DEPLOYING state when
> creating consumer input channels.
> (We had a bogus fix for this in FLINK-3232. With that "fix" we actually did
> not fix anything correctly and instead doubled the number of schedule or
> update consumer messages we sent.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
