[
https://issues.apache.org/jira/browse/KAFKA-15376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17785869#comment-17785869
]
Divij Vaidya commented on KAFKA-15376:
--------------------------------------
Hey [~ckamal]
I think the motivation of this ticket to determine whether there are
alternative options to remove leader epoch. As an example, in current
implementation, if the non-current leader epoch chain becomes current, we will
end up losing data in remote. With this ticket we wanted to explore if we can
choose to retain all non-current leader epoch chain (for case when one of them
may become a current chain) and leave the garbage collection to RSM. You can
find the context of the conversation at
[https://github.com/apache/kafka/pull/13561#discussion_r1298029817]
I am re-opening this ticket. Please add your thoughts here if you still think
that this should be resolved.
> Explore options of removing data earlier to the current leader's leader epoch
> lineage for topics enabled with tiered storage.
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-15376
> URL: https://issues.apache.org/jira/browse/KAFKA-15376
> Project: Kafka
> Issue Type: Task
> Components: core
> Reporter: Satish Duggana
> Assignee: Satish Duggana
> Priority: Major
> Fix For: 3.7.0
>
>
> Followup on the discussion thread:
> [https://github.com/apache/kafka/pull/13561#discussion_r1288778006]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
