You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Hangxiang Yu (Jira)" <ji...@apache.org> on 2022/12/12 08:26:00 UTC
[jira] [Assigned] (FLINK-30251) Move the IO with DFS during abort checkpoint to an asynchronous thread.
[ https://issues.apache.org/jira/browse/FLINK-30251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hangxiang Yu reassigned FLINK-30251:
------------------------------------
Assignee: ming li
> 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
> 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)