You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2018/05/30 10:06:00 UTC

[jira] [Updated] (FLINK-9413) Tasks can fail with PartitionNotFoundException if consumer deployment takes too long

     [ https://issues.apache.org/jira/browse/FLINK-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aljoscha Krettek updated FLINK-9413:
------------------------------------
    Affects Version/s: 1.4.0

> Tasks can fail with PartitionNotFoundException if consumer deployment takes too long
> ------------------------------------------------------------------------------------
>
>                 Key: FLINK-9413
>                 URL: https://issues.apache.org/jira/browse/FLINK-9413
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Coordination
>    Affects Versions: 1.4.0, 1.5.0, 1.6.0
>            Reporter: Till Rohrmann
>            Priority: Critical
>
> {{Tasks}} can fail with a {{PartitionNotFoundException}} if the deployment of the producer takes too long. More specifically, if it takes longer than the {{taskmanager.network.request-backoff.max}}, then the {{Task}} will give up and fail.
> The problem is that we calculate the {{InputGateDeploymentDescriptor}} for a consuming task once the producer has been assigned a slot but we do not wait until it is actually running. The problem should be fixed if we wait until the task is in state {{RUNNING}} before assigning the result partition to the consumer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)