[ https://issues.apache.org/jira/browse/KAFKA-15038 ]


    Owen C.H. Leung deleted comment on KAFKA-15038:
    -----------------------------------------

was (Author: JIRAUSER300460):
[~divijvaidya] I've done a bit diving into the existing code and I'm happy to 
pick this up. Will create PR soon

 

> Use topic id/name mapping from the Metadata cache in the RemoteLogManager
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-15038
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15038
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: core
>            Reporter: Alexandre Dupriez
>            Priority: Minor
>
> Currently, the {{RemoteLogManager}} maintains its own cache of topic name to 
> topic id 
> [[1]|https://github.com/apache/kafka/blob/trunk/core/src/main/java/kafka/log/remote/RemoteLogManager.java#L138]
>  using the information provided during leadership changes, and removing the 
> mapping upon receiving the notification of partition stopped.
> It should be possible to re-use the mapping in a broker's metadata cache, 
> removing the need for the RLM to build and update a local cache thereby 
> duplicating the information in the metadata cache. It also allows to preserve 
> a single source of authority regarding the association between topic names 
> and ids.
> [1] 
> https://github.com/apache/kafka/blob/trunk/core/src/main/java/kafka/log/remote/RemoteLogManager.java#L138



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to