[jira] [Commented] (FLINK-4714) Set task state to RUNNING after state has been restored

["Piotr Nowojski (Jira)" <ji...@apache.org>]

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

Piotr Nowojski commented on FLINK-4714:
---------------------------------------

Technically speaking FLINK-17012 is duplicating this ticket, but I think it has much [more up to date discussion|https://issues.apache.org/jira/browse/FLINK-17012?focusedCommentId=17091539&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17091539] and proposal how to solve this, so I would propose to close FLINK-4714 and supersede it with FLINK-17012

> Set task state to RUNNING after state has been restored
> -------------------------------------------------------
>
>                 Key: FLINK-4714
>                 URL: https://issues.apache.org/jira/browse/FLINK-4714
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Task
>    Affects Versions: 1.2.0
>            Reporter: Till Rohrmann
>            Assignee: Wei-Che Wei
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The task state is set to {{RUNNING}} as soon as the {{Task}} is executed. That, however, happens before the state of the {{StreamTask}} invokable has been restored. As a result, the {{CheckpointCoordinator}} starts to trigger checkpoints even though the {{StreamTask}} is not ready.
> In order to avoid aborting checkpoints and properly start it, we should switch the task state to {{RUNNING}} after the state has been restored.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)