root
/
kafka
mirror of https://github.com/apache/kafka.git
1
0
Fork 0
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Revert "KAFKA-16101: Additional fixes on KRaft migration documentation (#15287)" 

This reverts commit 46d76269fa.
This commit is contained in:
Colin P. McCabe 2024-02-01 16:17:18 -08:00
parent 12ce9c7f98
commit b8ad609541
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/ops.html
View File

@ -4045,7 +4045,7 @@ listeners=CONTROLLER://:9093
<li> <li>
On each broker, remove the <code>zookeeper.metadata.migration.enable</code>, On each broker, remove the <code>zookeeper.metadata.migration.enable</code>,
<code>controller.listener.names</code>, and <code>controller.quorum.voters</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. Then perform a rolling restart of all brokers.
</li> </li>
<li> <li>
@ -4054,7 +4054,7 @@ listeners=CONTROLLER://:9093
</ul> </ul>
</td> </td>
<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. time that the cluster lacks a controller.
</td> </td>
</tr> </tr>
@ -4063,8 +4063,7 @@ listeners=CONTROLLER://:9093
<td> <td>
<ul> <ul>
<li> <li>
On each broker, remove the <code>process.roles</code> configuration, On each broker, remove the <code>process.roles</code> configuration, and
replace the <code>node.id</code> with <code>broker.id</code> and
restore the <code>zookeeper.connect</code> configuration to its previous value. restore the <code>zookeeper.connect</code> configuration to its previous value.
If your cluster requires other ZooKeeper configurations for brokers, such as If your cluster requires other ZooKeeper configurations for brokers, such as
<code>zookeeper.ssl.protocol</code>, re-add those configurations as well. <code>zookeeper.ssl.protocol</code>, re-add those configurations as well.
@ -4080,7 +4079,7 @@ listeners=CONTROLLER://:9093
<li> <li>
On each broker, remove the <code>zookeeper.metadata.migration.enable</code>, On each broker, remove the <code>zookeeper.metadata.migration.enable</code>,
<code>controller.listener.names</code>, and <code>controller.quorum.voters</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. Then perform a second rolling restart of all brokers.
</li> </li>
<li> <li>
@ -4091,7 +4090,7 @@ listeners=CONTROLLER://:9093
<td> <td>
<ul> <ul>
<li> <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. time that the cluster lacks a controller.
</li> </li>
<li> <li>