[
https://issues.apache.org/jira/browse/FLINK-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15723031#comment-15723031
]
ASF GitHub Bot commented on FLINK-5114:
---------------------------------------
Github user uce commented on the issue:
https://github.com/apache/flink/pull/2913
> Why is that necessary? Can we not just assume that if the attempt is not
equal to the current execution attempt, then the status is some form of
"disposed".
It's not necessary. It's perfectly fine to do it as you describe. Not
having the `currentExecution` set to the producer execution means that the
producer was restarted (hence cancelled or failed). This only made the handling
in `Task` easier, but it should not dictate this change in the
`ExecutionVertex`. I'll change that to only check the `currentExecution` and
handle it accordingly.
> PartitionState update with finished execution fails
> ---------------------------------------------------
>
> Key: FLINK-5114
> URL: https://issues.apache.org/jira/browse/FLINK-5114
> Project: Flink
> Issue Type: Bug
> Components: Network
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
>
> If a partition state request is triggered for a producer that finishes before
> the request arrives, the execution is unregistered and the producer cannot be
> found. In this case the PartitionState returns null and the job fails.
> We need to check the producer location via the intermediate result partition
> in this case.
> See here: https://api.travis-ci.org/jobs/177668505/log.txt?deansi=true
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
