[ 
https://issues.apache.org/jira/browse/FLINK-38909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

CHANHAE OH updated FLINK-38909:
-------------------------------
    Description: 
When saving data to S3 in Flink with a specified checkpoint path, MinIO 
automatically creates a {{default.txt}} file in that path when it is created.

 

As a result, the checkpoint directory is recognized as non-empty, preventing 
the checkpoint from being deleted.

This issue makes it impossible to delete unnecessary checkpoints, causing 
difficulties in resource management. I am raising this issue to address the 
problem.
 
 

  was:
When saving data to S3 in Flink with a specified checkpoint path, MinIO 
automatically creates a {{default.txt}} file in that path when it is created. 
As a result, the checkpoint directory is recognized as non-empty, preventing 
the checkpoint from being deleted. This issue makes it impossible to delete 
unnecessary checkpoints, causing difficulties in resource management. I am 
raising this issue to address the problem.
 
 


> Unable to delete S3 checkpoint due to presence of default file
> --------------------------------------------------------------
>
>                 Key: FLINK-38909
>                 URL: https://issues.apache.org/jira/browse/FLINK-38909
>             Project: Flink
>          Issue Type: Bug
>          Components: API / Core
>    Affects Versions: 2.0.1, 2.2.0, 2.1.1
>            Reporter: CHANHAE OH
>            Priority: Minor
>             Fix For: 2.0.1
>
>
> When saving data to S3 in Flink with a specified checkpoint path, MinIO 
> automatically creates a {{default.txt}} file in that path when it is created.
>  
> As a result, the checkpoint directory is recognized as non-empty, preventing 
> the checkpoint from being deleted.
> This issue makes it impossible to delete unnecessary checkpoints, causing 
> difficulties in resource management. I am raising this issue to address the 
> problem.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to