[
https://issues.apache.org/jira/browse/FLINK-27608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537500#comment-17537500
]
zlzhang0122 commented on FLINK-27608:
-------------------------------------
[~Thesharing] Thanks for your detailed reply. I think the scenario you have
mentioned is very useful and is one of the scenarios. The case I have met is
another scenario, in that case, the akka message maybe miss or timeout, and I
have upload a log about that to describe it.Correct me if I'm wrong?
> Flink may throw PartitionNotFound Exception if the downstream task reached
> Running state earlier than it's upstream task
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-27608
> URL: https://issues.apache.org/jira/browse/FLINK-27608
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Network
> Affects Versions: 1.14.2
> Reporter: zlzhang0122
> Priority: Major
> Attachments: exception.txt
>
>
> Flink streaming job deployment may throw PartitionNotFound Exception if the
> downstream task reached Running state earlier than its upstream task and
> after maximum backoff for partition requests passed.But the config of
> taskmanager.network.request-backoff.max is not eay to decide. Can we use a
> loop awaiting the upstream task partition be ready?
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
