[
https://issues.apache.org/jira/browse/KAFKA-16454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamal Chandraprakash updated KAFKA-16454:
-----------------------------------------
Description:
When restarting the broker, we are reading from the beginning of the
{{__remote_log_metadata}} topic to reconstruct the state of remote log
segments, instead we can snapshot the state of remote log segments under each
partition directory.
Previous work to snapshot the state of the remote log metadata are removed as
the solution is incomplete:
https://github.com/apache/kafka/pull/15636
was:
When restarting the broker, we are reading from the beginning of the
{{__remote_log_metadata}} topic to reconstruct the state of remote log
segments, instead we can snapshot the state of remote log segments under each
partition directory.
Previous work to snapshot the state of the remote log metadata are removed as
the solution is not complete.
https://github.com/apache/kafka/pull/15636
> Snapshot the state of remote log metadata for all the partitions
> ----------------------------------------------------------------
>
> Key: KAFKA-16454
> URL: https://issues.apache.org/jira/browse/KAFKA-16454
> Project: Kafka
> Issue Type: Task
> Reporter: Kamal Chandraprakash
> Priority: Major
> Labels: tiered-storage
>
> When restarting the broker, we are reading from the beginning of the
> {{__remote_log_metadata}} topic to reconstruct the state of remote log
> segments, instead we can snapshot the state of remote log segments under each
> partition directory.
> Previous work to snapshot the state of the remote log metadata are removed as
> the solution is incomplete:
> https://github.com/apache/kafka/pull/15636
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
