[
https://issues.apache.org/jira/browse/KAFKA-16378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838635#comment-17838635
]
Ivan Yurchenko commented on KAFKA-16378:
----------------------------------------
This was a problem in the RemoteStorageManager. I'll close this issue.
[~jianbin] feel free to reopen if you think this needs more attention.
> Under tiered storage, deleting local logs does not free disk space
> ------------------------------------------------------------------
>
> Key: KAFKA-16378
> URL: https://issues.apache.org/jira/browse/KAFKA-16378
> Project: Kafka
> Issue Type: Bug
> Components: Tiered-Storage
> Affects Versions: 3.7.0
> Reporter: Jianbin Chen
> Priority: Major
> Attachments: image-2024-03-15-09-33-13-903.png
>
>
> Of course, this is an occasional phenomenon, as long as the tiered storage
> topic triggered the deletion of the local log action, there is always the
> possibility of residual file references, but these files on the local disk is
> already impossible to find!
> I use the implementation as: [Aiven-Open/tiered-storage-for-apache-kafka:
> RemoteStorageManager for Apache Kafka® Tiered Storage
> (github.com)|https://github.com/Aiven-Open/tiered-storage-for-apache-kafka]
> I also filed an issue in their community, which also contains a full
> description of the problem
> [Disk space not released · Issue #513 ·
> Aiven-Open/tiered-storage-for-apache-kafka
> (github.com)|https://github.com/Aiven-Open/tiered-storage-for-apache-kafka/issues/513]
> !image-2024-03-15-09-33-13-903.png!
> You can clearly see in this figure that the kafka log has already output the
> log of the operation that deleted the log, but the log is still referenced
> and the disk space has not been released
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
