[
https://issues.apache.org/jira/browse/FLINK-4933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621570#comment-15621570
]
ASF GitHub Bot commented on FLINK-4933:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/2700
Thanks for the review @uce. This is a problem which is relevant for the
current master. It could make the `ExecutionGraph` go into state `FAILED` when
being in state `RESTARTING` in case that the `scheduleOrUpdateConsumers` call
failed.
Will rebase the PR because it was based on the failing
`SpanningRecordSerializerTest`.
> ExecutionGraph.scheduleOrUpdateConsumers can fail the ExecutionGraph
> --------------------------------------------------------------------
>
> Key: FLINK-4933
> URL: https://issues.apache.org/jira/browse/FLINK-4933
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination
> Affects Versions: 1.2.0, 1.1.3
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Fix For: 1.2.0, 1.1.4
>
>
> Currently the {{ExecutionGraph.scheduleOrUpdateConsumers}} can fail the whole
> {{ExecutionGraph}} if it cannot find the corresponding {{Execution}}. This
> situation can occur in the restarting scenario where we have a late callback
> trying to update its consumers. In this case, the call should forward the
> exception back to the caller and not fail the {{ExecutionGraph}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
