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

ASF GitHub Bot updated FLINK-39786:
-----------------------------------
    Labels: pull-request-available  (was: )

> closeForCommit() leaks orphan multipart uploads on upload failure
> -----------------------------------------------------------------
>
>                 Key: FLINK-39786
>                 URL: https://issues.apache.org/jira/browse/FLINK-39786
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Connectors / FileSystem
>            Reporter: Samrat Deb
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.4.0
>
>
> If uploadCurrentPart() throws after closed=true, the method exits without 
> aborting the MPU and close() short-circuits on closed. The upload sits in S3 
> indefinitely. Even when
> close() does run, an abortMultiPartUpload failure is only WARNwith a comment 
> hoping bucket lifecycle rules clean up. Practically, most buckets don't have 
> AbortIncompleteMultipartUpload configured.



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

Reply via email to