[
https://issues.apache.org/jira/browse/KAFKA-20207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Wu updated KAFKA-20207:
-----------------------------
Description:
This should enforce the following invariants:
* Whenever a MV that supports this feature is persisted to disk, the
ClusterIdRecord is persisted alongside it
** This is enforceable on the write path for MV: during node formatting, when
the active controller performs the bootstrap metadata write, when upgrading the
MV to a MV that supports this feature
* There is no ClusterIdRecord in the metadata log if the MV of the cluster
does NOT support this feature
* There is at most one ClusterIdRecord in the metadata log if the MV does
support this feature
> Handle the new ClusterIdRecord
> ------------------------------
>
> Key: KAFKA-20207
> URL: https://issues.apache.org/jira/browse/KAFKA-20207
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Kevin Wu
> Assignee: Kevin Wu
> Priority: Major
>
> This should enforce the following invariants:
> * Whenever a MV that supports this feature is persisted to disk, the
> ClusterIdRecord is persisted alongside it
> ** This is enforceable on the write path for MV: during node formatting,
> when the active controller performs the bootstrap metadata write, when
> upgrading the MV to a MV that supports this feature
> * There is no ClusterIdRecord in the metadata log if the MV of the cluster
> does NOT support this feature
> * There is at most one ClusterIdRecord in the metadata log if the MV does
> support this feature
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
