[
https://issues.apache.org/jira/browse/FLINK-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Wysakowicz updated FLINK-17012:
-------------------------------------
Release Note: Task's RUNNING state was split into two states: INITIALIZING
and RUNNING. Task is INITIALIZING while state is initialising and in case of
unaligned checkpoints, until all of the in-flight data has been recovered.
(was: Task's RUNNING state was split into two states: RECOVERING and RUNNING.
Task is RECOVERING while state is initialising and in case of unaligned
checkpoints, until all of the in-flight data has been recovered.)
> Expose stage of task initialization
> -----------------------------------
>
> Key: FLINK-17012
> URL: https://issues.apache.org/jira/browse/FLINK-17012
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Task
> Reporter: Wenlong Lyu
> Assignee: Anton Kalashnikov
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.0
>
>
> Currently a task switches to running before fully initialized, does not take
> state initialization and operator initialization(#open ) in to account, which
> may take long time to finish. As a result, there would be a weird phenomenon
> that all tasks are running but throughput is 0.
> I think it could be good if we can expose the initialization stage of tasks.
> What to you think?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
