You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Satish Duggana (Jira)" <ji...@apache.org> on 2023/06/01 13:11:00 UTC

[jira] [Updated] (KAFKA-15047) Handle rolling segments when the active segment's retention is breached incase of tiered storage is enabled.

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

Satish Duggana updated KAFKA-15047:
-----------------------------------
    Description: 
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. 

> 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)