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-4912) Introduce RECONCILING state in ExecutionGraph
Date Thu, 09 Feb 2017 14:03:42 GMT

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

ASF GitHub Bot commented on FLINK-4912:

Github user StephanEwen commented on the issue:

    Given that this only extends the enum and does not add changes to the state transitions,
we can merge this.

> Introduce RECONCILING state in ExecutionGraph
> ---------------------------------------------
>                 Key: FLINK-4912
>                 URL: https://issues.apache.org/jira/browse/FLINK-4912
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Distributed Coordination
>            Reporter: Stephan Ewen
>            Assignee: Zhijiang Wang
> This is part of the non-disruptive JobManager failure recovery.
> I suggest to add a JobStatus and ExecutionState {{RECONCILING}}.
> If a job is started on a that JobManager for master recovery (tbd how to determine that)
the {{ExecutionGraph}} and the {{Execution}}s start in the reconciling state.
> From {{RECONCILING}}, tasks can go to {{RUNNING}} (execution reconciled with TaskManager)
or to {{FAILED}}.

This message was sent by Atlassian JIRA

View raw message