[
https://issues.apache.org/jira/browse/FLINK-30251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17643730#comment-17643730
]
ming li commented on FLINK-30251:
---------------------------------
hi, [~Yanfei Lei]. I re-read FLINK-28984, it seems that it is a different
problem from ours, can we first move the synchronous IO to the asynchronous
thread to solve the problem of data not being processed? The problem of
FLINK-28984 can be fixed in other issues.
> 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)
