flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4932) Don't let ExecutionGraph fail when in state Restarting
Date Mon, 31 Oct 2016 08:01:12 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15621555#comment-15621555

ASF GitHub Bot commented on FLINK-4932:

Github user tillrohrmann commented on the issue:

    Thanks for the review @uce. @StephanEwen actually discovered this problem. The problem
was related to #2700. When the scheduleOrUpdateConsumers call was triggered when in state
restarting due to a late rpc, it would fail the complete `ExecutionGraph`, because it could
not find the respective `Execution`.
    Will rebase the PR, because release-1.1 contained a problem which prevented it from building.

> Don't let ExecutionGraph fail when in state Restarting
> ------------------------------------------------------
>                 Key: FLINK-4932
>                 URL: https://issues.apache.org/jira/browse/FLINK-4932
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Coordination
>    Affects Versions: 1.2.0, 1.1.4
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>             Fix For: 1.2.0, 1.1.4
> When in state {{RESTARTING}} it is possible to fail the {{ExecutionGraph}}. This should
not be possible, since in state {{RESTARTING}} there should be no action performed which can
fail the {{ExecutionGraph}}.

This message was sent by Atlassian JIRA

View raw message