[
https://issues.apache.org/jira/browse/FLINK-30251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688934#comment-17688934
]
Piotr Nowojski edited comment on FLINK-30251 at 2/15/23 8:43 AM:
-----------------------------------------------------------------
Note, [we had a quick discussion in the
PR|https://github.com/apache/flink/pull/21503#discussion_r1100231851] about
which thread pool to actually use, and decided to use the existing async thread
pool, but also to limit it's size.
merged commit d24760b into apache:master
was (Author: pnowojski):
merged commit d24760b into apache:master
> 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
> Assignee: ming li
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.0
>
> 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)
