[
https://issues.apache.org/jira/browse/FLINK-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897289#comment-15897289
]
ASF GitHub Bot commented on FLINK-4714:
---------------------------------------
Github user tony810430 commented on the issue:
https://github.com/apache/flink/pull/3474
Hi @StephanEwen
This suggestion seems to use constructor to set `Environment` instead of
using `setEnvironment(env)` method and may not need it any more.
Use the constructor to initialize other setting after `Environment` has
been set up if those are needed to be set up before `invoke()`. For example:
`StreamTask`.
If I misunderstand anything, please correct me. Thank you.
> 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: Wei-Che Wei
>
> 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)
