[
https://issues.apache.org/jira/browse/KAFKA-15047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731471#comment-17731471
]
Henry Cai commented on KAFKA-15047:
-----------------------------------
I created a topic with local.retention.ms=120000 (2 minutes)
```
bin/kafka-topics.sh --bootstrap-server localhost:9092 --create --topic topic1
--config remote.storage.enable=true --config segment.bytes=512000 --config
retention.ms=360000000 --config local.retention.ms=120000
```
The segments are copied to remote storage, but the local segments are not
cleaned up after 2 minutes by cleaner thread.
>From the code in trunk as of 6/12/2023, it doesn't looks like
>RemoteLogConfig.localRetentionMs is being used anywhere, I guess the code in
>UnifiedLog.RetentionMsBreach() is supposed to use localRetentionMs, but the
>code is not there.
This is not about current active segment, it's about the older segments.
Should I create a new JIRA?
> Handle rolling segments when the active segment's retention is breached
> incase of tiered storage is enabled.
> ------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-15047
> URL: https://issues.apache.org/jira/browse/KAFKA-15047
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Satish Duggana
> Assignee: Kamal Chandraprakash
> Priority: Major
>
> Active segments are not copied by remote storage subsystem. But they can be
> eligible for retention cleanup.
> So, we need to roll the active segment incase remote storage is enabled so
> that this can be copied by the remote storage subsystem and eventually picked
> up for retention cleanup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
