You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Wei-Che Wei (JIRA)" <ji...@apache.org> on 2017/02/25 05:10:44 UTC

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

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

Wei-Che Wei edited comment on FLINK-4714 at 2/25/17 5:10 AM:
-------------------------------------------------------------

Hi [~Andrew Efimov]
Are you still working on this task? If not, I can also work on it, because the task I want to work on is blocked by this issue.


was (Author: tonywei):
Hi Andrew, are you still working on the task? If not, I can also work on it, because the task I want to work on is blocked by this issue.

> 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: Distributed Coordination, State Backends, Checkpointing
>    Affects Versions: 1.2.0
>            Reporter: Till Rohrmann
>            Assignee: Andrew Efimov
>
> 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
(v6.3.15#6346)