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

Posted to jira@kafka.apache.org by "loboxu (Jira)" <ji...@apache.org> on 2021/05/24 08:43:00 UTC

[jira] [Assigned] (KAFKA-12461) Extend LogManager to cover the metadata topic

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

loboxu reassigned KAFKA-12461:
------------------------------

    Assignee: loboxu

> Extend LogManager to cover the metadata topic
> ---------------------------------------------
>
>                 Key: KAFKA-12461
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12461
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Jason Gustafson
>            Assignee: loboxu
>            Priority: Major
>
> The `@metadata` topic is not managed by `LogManager` since it uses a new snapshot-based retention policy. This means that it is not covered by the recovery and high watermark checkpoints. It would be useful to fix this. We can either extend `LogManager` so that it is aware of the snapshotting semantics implemented by the `@metadata` topic, or we can create something like a `RaftLogManager`.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)