[ https://issues.apache.org/jira/browse/FLINK-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079187#comment-17079187 ]
Chesnay Schepler commented on FLINK-17012: ------------------------------------------ I agree that a sentinel value will not work, it messes up aggregations and alerts. I feel like external systems should be able to handle this by considering all tasks for a submitted job to be in an initializing state until they have processed the first record. > 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)