[
https://issues.apache.org/jira/browse/FLINK-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095381#comment-17095381
]
Stephan Ewen commented on FLINK-17012:
--------------------------------------
If the "unspilling" part of unaligned checkpoints happens when it is already in
RUNNING - would that be a problem for the meaning of that metric?
This is, after all, already processing data with involvement of operator code,
not purely state-loading I/O.
It might show more utilization that usual during that phase (unspilling I/O in
addition to processing load); is that the main concern?
> 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)
