[
https://issues.apache.org/jira/browse/KAFKA-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-20609.
------------------------------------
Fix Version/s: 4.5.0
Resolution: Fixed
> Use the lastModifiedTime to replace furture timestamp in deleting retentions
> -----------------------------------------------------------------------------
>
> Key: KAFKA-20609
> URL: https://issues.apache.org/jira/browse/KAFKA-20609
> Project: Kafka
> Issue Type: Improvement
> Reporter: Chia-Ping Tsai
> Assignee: Muralidhar Basani
> Priority: Major
> Fix For: 4.5.0
>
>
> The system uploads segment files with future data to remote storage
> immediately. By contrast, the local files can't be deleted due to the future
> timestamp, so maybe we should find another anchor to replace it, such as
> lastModifiedTime. In the grand scheme of things, they will be deleted by
> other factors like size limits, but fixing it can avoid counter-intuitive
> logic for users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
