You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Rui Xia (Jira)" <ji...@apache.org> on 2024/11/22 03:22:00 UTC
[jira] [Commented] (FLINK-36768) Empty Checkpoint Directory created when older checkpoint fails due to timeout and the checkpoint interval is same
[ https://issues.apache.org/jira/browse/FLINK-36768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17900228#comment-17900228 ]
Rui Xia commented on FLINK-36768:
---------------------------------
Hi Thomas, thank you for reporting this. From your description, I am not sure which chk-<id> is not properly deleted. Could you provide a more concrete example for your condition. For example, chk-1 trigger -> chk-1 timeout -> at the same time chk-2 trigger, chk-xxx cp directory is not cleaned.
BTW, 1.12.1 is a old flink version (2 years ago). You may use the latest version and check whether the same problem is still existed or not.
> Empty Checkpoint Directory created when older checkpoint fails due to timeout and the checkpoint interval is same
> ------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-36768
> URL: https://issues.apache.org/jira/browse/FLINK-36768
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.12.1
> Reporter: Eaugene Thomas
> Priority: Minor
>
> When the checkpoint interval equals the checkpoint timeout, and the failure threshold is reached, the asynchronous checkpoint trigger starts. However, due to an internal restart, the tombstone directory ({{{}chk-<id>{}}}) is not cleared.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)