[
https://issues.apache.org/jira/browse/FLINK-39786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18085127#comment-18085127
]
Arvind Kandpal commented on FLINK-39786:
----------------------------------------
Hi Team, I looked into this issue and it's a critical leak when
{{uploadCurrentPart()}} fails after {{closed}} is set to true. I'd like to fix
this exception-handling flow to ensure the multipart upload is properly
aborted. Can you please assign this to me?
[~samrat007] if you are not doing can I pick this ?
> 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
> 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)
