[
https://issues.apache.org/jira/browse/FLINK-13013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Nowojski resolved FLINK-13013.
------------------------------------
Resolution: Fixed
Release Note: Because we are requesting partitions sooner (now we are
requesting partitions before initialise operator states), partitions request
re-triggering will also happen sooner, so the incremental back of counter will
start counting also sooner. In some cases that might mean users should increase
{{taskmanager.network.request-backoff.max}} value in order to have the same
effective request partitions time out as it was in Flink 1.8.
> Make sure that SingleInputGate can always request partitions
> ------------------------------------------------------------
>
> Key: FLINK-13013
> URL: https://issues.apache.org/jira/browse/FLINK-13013
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Network
> Affects Versions: 1.9.0
> Reporter: Piotr Nowojski
> Assignee: Piotr Nowojski
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently {{SingleInputGate}} requests partitions only on the first attempt
> to fetch the data. Before requesting partitions, no data availability
> notifications can get through. This doesn't work well with a new non blocking
> {{InputGate}} interface, since on newly created {{SingleInputGates,}}
> {{InputGate#isAvailable()}} might return not available, and it will be only
> able to switch to available, after first call to
> {{SingleInputGate#pollNext()}}. However this might never happen, since caller
> could be waiting indefinitely on {{SingleInputGate#isAvailable()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
