This is an automated email from the ASF dual-hosted git repository.
cmccabe pushed a commit to branch KAFKA-15311
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/KAFKA-15311 by this push:
new 58809827ab1 KAFKA-15311: Fix docs about reverting to ZooKeeper mode
during KRaft migration (#14682)
58809827ab1 is described below
commit 58809827ab12bc0bf1a3d9adc5bcc3c63a72fa5e
Author: Liu Zeyu <[email protected]>
AuthorDate: Mon Nov 13 16:09:13 2023 -0800
KAFKA-15311: Fix docs about reverting to ZooKeeper mode during KRaft
migration (#14682)
Reviewers: Qichao Chu , Colin P. McCabe <[email protected]>
---
docs/ops.html | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/docs/ops.html b/docs/ops.html
index bf66b18a479..88a8a80851b 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -3602,7 +3602,6 @@ foo
<ul>
<li>Supporting JBOD configurations with multiple storage directories</li>
- <li>Modifying certain dynamic configurations on the standalone KRaft
controller</li>
</ul>
<h4 class="anchor-heading"><a id="kraft_zk_migration"
class="anchor-link"></a><a href="#kraft_zk_migration">ZooKeeper to KRaft
Migration</a></h4>
@@ -3613,8 +3612,6 @@ foo
<a href="https://issues.apache.org/jira/projects/KAFKA";
target="_blank">project JIRA</a> and the "kraft" component.
</p>
- </p>
-
<h3>Terminology</h3>
<ul>
<li>Brokers that are in <b>ZK mode</b> store their metadata in Apache
ZooKeeper. This is the old mode of handling metadata.</li>
@@ -3624,12 +3621,13 @@ foo
<h3>Migration Phases</h3>
In general, the migration process passes through several phases.
+
+ For
<ul>
- <li>In the <b>initial phase</b>, all the brokers are in ZK mode, and there
is a ZK-based controller.</li>
- <li>During the <b>initial metadata load</b>, a KRaft quorum loads the
metadata from ZooKeeper,</li>
- <li>In <b>hybrid phase</b>, some brokers are in ZK mode, but there is a
KRaft controller.</li>
- <li>In <b>dual-write phase</b>, all brokers are KRaft, but the KRaft
controller is continuing to write to ZK.</li>
- <li>When the migration has been <b>finalized</b>, we no longer write
metadata to ZooKeeper.</li>
+ <li>In the <b>pre-migration phase</b>, all the brokers are in ZK mode, and
there is a ZK-based controller quorum. But a KRaft controller quorum has been
provisioned and has migration enabled</li>
+ <li>During the <b>initial metadata load</b>, a KRaft quorum loads the
metadata from ZooKeeper.</li>
+ <li>In <b>migration phase</b>, all brokers are transitioning from ZK to
KRaft. The KRaft controller has begun the data migration, brokers are being
restarted, dual-writes are in progress. The KRaft controller is continuing to
write to ZK.</li>
+ <li>In the post migration phase, when the migration has been
<b>finalized</b>, we no longer write metadata to ZooKeeper.</li>
</ul>
<h3>Limitations</h3>
@@ -3639,7 +3637,7 @@ foo
a migration, or you may break the cluster.</li>
<li>After the migration has been finalized, it is not possible to revert
back to ZooKeeper mode.</li>
<li><a href="#kraft_missing">As noted above</a>, some features are not
fully implemented in KRaft mode. If you are
- using one of those features, you will not be able to migrate to KRaft
yet.</li>
+ using one of those features, you are not able to migrate to KRaft
yet.</li>
</ul>
<h3>Preparing for migration</h3>
