[kafka-site] 01/01: Fix some errors and omissions in the migration docs

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davidarthur pushed a commit to branch KAFKA-14692-fix-migration-docs
in repository https://gitbox.apache.org/repos/asf/kafka-site.git

commit 7ff104dbe4904fce792fb99bfe17f2b7e446808a
Author: David Arthur <mu...@gmail.com>
AuthorDate: Wed Feb 8 12:53:40 2023 -0500

    Fix some errors and omissions in the migration docs
---
 34/ops.html | 28 +++++++++++++++++++++++-----
 1 file changed, 23 insertions(+), 5 deletions(-)

diff --git a/34/ops.html b/34/ops.html
index 9f35e49e..394fb5e1 100644
--- a/34/ops.html
+++ b/34/ops.html
@@ -3580,6 +3580,11 @@ foo
     <li>Other features <a href="#kraft_missing">not yet supported in KRaft</a></li>
   </ul>
 
+  <p>
+    Please report issues with ZooKeeper to KRaft migration using the
+    <a href="https://issues.apache.org/jira/projects/KAFKA" target="_blank">project JIRA</a> and the "kraft" component.
+  </p>
+
   <h3>Terminology</h3>
   <p>
     In this documentation, we use the term "migration" to refer to the process to changing a Kafka cluster's metadata
@@ -3615,8 +3620,21 @@ foo
   <h3>Provisioning the KRaft controller quorum</h3>
   <p>
     Two things are needed before the migration can begin. The brokers must be configured to support the migration and
-    a KRaft controller quorum must be deployed. For the KRaft deployment, please refer to <a href="#kraft_config">the above documentation</a>.
-    The KRaft controllers should be provisioned with the latest <code>metadata.version</code> of "3.4".
+    a KRaft controller quorum must be deployed. The KRaft controllers should be provisioned with the same cluster ID as
+    the existing Kafka cluster. This can be found by examining one of the "meta.properties" files in the data directories
+    of the brokers, or by running the following command.
+  </p>
+
+  <pre>
+    ./bin/zookeeper-shell.sh localhost:2181 get /cluster/id
+  </pre>
+
+  <p>
+    The KRaft controller quorum should also be provisioned with the latest <code>metadata.version</code> of "3.4".
+    For further instructions on KRaft deployment, please refer to <a href="#kraft_config">the above documentation</a>.
+  </p>
+
+  <p>
     In addition to the standard KRaft configuration, the KRaft controllers will need to enable support for the migration
     as well as provide ZooKeeper connection configuration.
   </p>
@@ -3625,7 +3643,7 @@ foo
     # Sample KRaft cluster controller.properties listening on 9093
     process.roles=controller
     node.id=3000
-    controller.quorum.voters=1@localhost:9093
+    controller.quorum.voters=3000@localhost:9093
     controller.listener.names=CONTROLLER
     listeners=CONTROLLER://:9093
 
@@ -3710,8 +3728,8 @@ foo
     # Don't set the IBP, KRaft uses "metadata.version" feature flag
     # inter.broker.protocol.version=3.4
 
-    # Keep the migration enabled
-    zookeeper.metadata.migration.enable=true
+    # Remove the migration enabled flag
+    # zookeeper.metadata.migration.enable=true
 
     # Remove ZooKeeper client configuration
     # zookeeper.connect=localhost:2181