You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/06/13 10:42:01 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 ]

Flink Jira Bot updated FLINK-9413:
----------------------------------
    Labels: auto-deprioritized-critical pull-request-available stale-major  (was: auto-deprioritized-critical pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> 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: Runtime / Coordination
>    Affects Versions: 1.4.0, 1.5.0, 1.6.0
>            Reporter: Till Rohrmann
>            Priority: Major
>              Labels: auto-deprioritized-critical, pull-request-available, stale-major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> {{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
(v8.3.4#803005)