[
https://issues.apache.org/jira/browse/KAFKA-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-16463:
---------------------------------
Description:
Throughout the process of a ZK to KRaft migration, the operator has the choice
to revert back to ZK mode. Once this is done, there will be a copy of the
metadata log on each broker in the cluster.
In order to re-attempt the migration in the future, this metadata log needs to
be deleted. This can be pretty burdensome to the operator for large clusters.
To improve this, we can automatically delete any metadata log present during
startup of a ZK broker. This is safe to do because the ZK broker will just
re-replicate the metadata log from the active controller. Once a broker
restarts as KRaft, it will stop doing this automatic deletion.
was:
Throughout the process of a ZK to KRaft migration, the operator has the choice
to revert back to ZK mode. Once this is done, there will be a copy of the
metadata log on each broker in the cluster.
In order to re-attempt the migration in the future, this metadata log needs to
be deleted. This can be pretty burdensome to the operator for large clusters.
To improve this, we can automatically delete any metadata log present during
startup of a ZK broker. This is safe to do because the ZK broker will just
re-replicate the metadata log from the active controller.
> Automatically delete metadata log directory on ZK brokers
> ---------------------------------------------------------
>
> Key: KAFKA-16463
> URL: https://issues.apache.org/jira/browse/KAFKA-16463
> Project: Kafka
> Issue Type: Improvement
> Reporter: David Arthur
> Assignee: David Arthur
> Priority: Minor
> Fix For: 3.8.0
>
>
> Throughout the process of a ZK to KRaft migration, the operator has the
> choice to revert back to ZK mode. Once this is done, there will be a copy of
> the metadata log on each broker in the cluster.
> In order to re-attempt the migration in the future, this metadata log needs
> to be deleted. This can be pretty burdensome to the operator for large
> clusters.
> To improve this, we can automatically delete any metadata log present during
> startup of a ZK broker. This is safe to do because the ZK broker will just
> re-replicate the metadata log from the active controller. Once a broker
> restarts as KRaft, it will stop doing this automatic deletion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
