[ https://issues.apache.org/jira/browse/FLINK-30251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644676#comment-17644676 ]
Yun Gao commented on FLINK-30251: --------------------------------- [~Ming Li] Hi sorry I might also need to complement one thing: as an alternative option, could you also have a double check if it is possible to limit the maximum of time to wait for closing to finish? > Move the IO with DFS during abort checkpoint to an asynchronous thread. > ----------------------------------------------------------------------- > > Key: FLINK-30251 > URL: https://issues.apache.org/jira/browse/FLINK-30251 > Project: Flink > Issue Type: Improvement > Components: Runtime / Checkpointing > Affects Versions: 1.16.0, 1.15.2 > Reporter: ming li > Priority: Major > Attachments: image-2022-11-30-19-10-51-226.png > > > Currently when the {{checkpoint}} fails, we process the abort message in the > Task's {{{}mailbox{}}}. We will close the output stream and delete the file > on DFS. > > However, when the {{checkpoint}} failure is caused by a DFS system failure > (for example, the namenode failure of HDFS), this operation may take a long > time or hang, and the task will not be able to process the data at this time. > > So I think we can put the operation of deleting files in an asynchronous > thread just like uploading checkpoint data asynchronously. > !image-2022-11-30-19-10-51-226.png|width=731,height=347! -- This message was sent by Atlassian Jira (v8.20.10#820010)