This is an automated email from the ASF dual-hosted git repository.
mimaison pushed a commit to branch 3.7
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/3.7 by this push:
new 434192e6c20 KAFKA-16005: Add details about rollback during ZK->KRaft
migration in docs (#15012)
434192e6c20 is described below
commit 434192e6c2011639f5e4a1449e8ae69d38ebda29
Author: Paolo Patierno <ppatie...@live.com>
AuthorDate: Thu Dec 14 14:59:29 2023 +0100
KAFKA-16005: Add details about rollback during ZK->KRaft migration in docs
(#15012)
Reviewers: Mickael Maison <mickael.mai...@gmail.com>, Luke Chen
<show...@gmail.com>
---
docs/ops.html | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/docs/ops.html b/docs/ops.html
index 85b683be245..c4be91cb0ad 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -3895,7 +3895,16 @@ controller.listener.names=CONTROLLER</pre>
<h3>Reverting to ZooKeeper mode During the Migration</h3>
While the cluster is still in migration mode, it is possible to revert to
ZK mode. In order to do this:
<ol>
- <li>One by one, take each KRaft broker down. Remove the
__cluster_metadata directory on the broker. Then, restart the broker in
ZooKeeper mode.</li>
+ <li>
+ For each KRaft broker:
+ <ul>
+ <li>Stop the broker.</li>
+ <li>Remove the __cluster_metadata directory on the broker.</li>
+ <li>Remove the <code>zookeeper.metadata.migration.enable</code>
configuration and the KRaft controllers related configurations like
<code>controller.quorum.voters</code>
+ and <code>controller.listener.names</code> from the broker
configuration properties file.</li>
+ <li>Restart the broker in ZooKeeper mode.</li>
+ </ul>
+ </li>
<li>Take down the KRaft quorum.</li>
<li>Using ZooKeeper shell, delete the controller node using <code>rmr
/controller</code>, so that a ZooKeeper-based broker can become the next
controller.</li>
</ol>
