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

Posted to jira@kafka.apache.org by "Alexandre Dupriez (Jira)" <ji...@apache.org> on 2023/05/30 10:11:00 UTC

[jira] [Updated] (KAFKA-15038) Use topic id/name mapping from the Metadata cache in the RemoteLogManager

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

Alexandre Dupriez updated KAFKA-15038:
--------------------------------------
    Summary: Use topic id/name mapping from the Metadata cache in the RemoteLogManager  (was: Use topic id/name mapping from the Metadata cache in RLM)

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