[
https://issues.apache.org/jira/browse/FLINK-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079409#comment-17079409
]
Wenlong Lyu commented on FLINK-17012:
-------------------------------------
[~chesnay] I think it is not a good choice to treat processing first record as
the signal of finishing initialization: when there is a filter in a job which
filters most of the records or there is no input for long time, we will make a
wrong decision. IMO, it would be perfect if we can add a new stage(state) for
task such as Initializing which can be easily visualized but it can hurt
compatibility, a separate metric maybe a good compromise?
> Expose stage of task initialization
> -----------------------------------
>
> Key: FLINK-17012
> URL: https://issues.apache.org/jira/browse/FLINK-17012
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics, Runtime / Task
> Reporter: Wenlong Lyu
> Priority: Major
>
> 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)
