[
https://issues.apache.org/jira/browse/FLINK-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080957#comment-17080957
]
Chesnay Schepler commented on FLINK-17012:
------------------------------------------
Non-numeric metrics are problematic as virtually no metric backend supports
them and use-cases for these are usually better satisfied via the REST API.
In fact I'd like get rid of them entirely (there is _literally_ 1), and not add
more of them as they are immediate technical debt as far as I'm concerned.
I would argue the same applies here. We've been wanting a separate
initialization state for tasks for a long time; good ol'
can't-do-savepoint-because-not-all-tasks-are-running despite everything saying
that they are.
> 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)
