[ 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 auto-deprioritized-major pull-request-available (was: auto-deprioritized-critical pull-request-available stale-major) Priority: Minor (was: Major) This issue was labeled "stale-major" 7 ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > 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: Minor > Labels: auto-deprioritized-critical, auto-deprioritized-major, > pull-request-available > 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)