You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by cm...@apache.org on 2024/02/02 00:17:31 UTC
(kafka) branch trunk updated: Revert "KAFKA-16101: Additional fixes on KRaft migration documentation (#15287)"
This is an automated email from the ASF dual-hosted git repository.
cmccabe pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/trunk by this push:
new b8ad609541b Revert "KAFKA-16101: Additional fixes on KRaft migration documentation (#15287)"
b8ad609541b is described below
commit b8ad609541bb8b224d16ce832a08f51017002bc1
Author: Colin P. McCabe <cm...@apache.org>
AuthorDate: Thu Feb 1 16:17:18 2024 -0800
Revert "KAFKA-16101: Additional fixes on KRaft migration documentation (#15287)"
This reverts commit 46d76269fa72020d3d56d9e41d6f337563152837.
---
docs/ops.html | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/docs/ops.html b/docs/ops.html
index eb8c7431665..8cb65549db6 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -4045,7 +4045,7 @@ listeners=CONTROLLER://:9093
<li>
On each broker, remove the <code>zookeeper.metadata.migration.enable</code>,
<code>controller.listener.names</code>, and <code>controller.quorum.voters</code>
- configurations.
+ configurations, and replace <code>node.id</code> with <code>broker.id</code>.
Then perform a rolling restart of all brokers.
</li>
<li>
@@ -4054,7 +4054,7 @@ listeners=CONTROLLER://:9093
</ul>
</td>
<td>
- It is important to perform the <code>zookeeper-shell.sh</code> step quickly together with rolling at least one broker (into pure ZooKeeper mode), to minimize the amount of
+ It is important to perform the <code>zookeeper-shell.sh</code> step quickly, to minimize the amount of
time that the cluster lacks a controller.
</td>
</tr>
@@ -4063,8 +4063,7 @@ listeners=CONTROLLER://:9093
<td>
<ul>
<li>
- On each broker, remove the <code>process.roles</code> configuration,
- replace the <code>node.id</code> with <code>broker.id</code> and
+ On each broker, remove the <code>process.roles</code> configuration, and
restore the <code>zookeeper.connect</code> configuration to its previous value.
If your cluster requires other ZooKeeper configurations for brokers, such as
<code>zookeeper.ssl.protocol</code>, re-add those configurations as well.
@@ -4080,7 +4079,7 @@ listeners=CONTROLLER://:9093
<li>
On each broker, remove the <code>zookeeper.metadata.migration.enable</code>,
<code>controller.listener.names</code>, and <code>controller.quorum.voters</code>
- configurations.
+ configurations. Replace <code>node.id</code> with <code>broker.id</code>.
Then perform a second rolling restart of all brokers.
</li>
<li>
@@ -4091,7 +4090,7 @@ listeners=CONTROLLER://:9093
<td>
<ul>
<li>
- It is important to perform the <code>zookeeper-shell.sh</code> step <b>quickly</b> together with rolling at least one broker (into pure ZooKeeper mode), to minimize the amount of
+ It is important to perform the <code>zookeeper-shell.sh</code> step <b>quickly</b>, to minimize the amount of
time that the cluster lacks a controller.
</li>
<li>