[ https://issues.apache.org/jira/browse/FLINK-17012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087462#comment-17087462 ]
Stephan Ewen commented on FLINK-17012: -------------------------------------- It is true that this needs a constructor written in a way to "clean up after itself" on exception. But the code for that is pretty much the same (can actually be a bit simpler) as in an "initialize()" method and a "cleanup()" method where the "cleanup()" method needs to understand how far the "initialize()" method got. > 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)