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

MINOR: Add a separate page for zk2kraft.html (#18961) 

Reviewers: mingdaoy <mingdaoy@gmail.com>, Ken Huang <s7133700@gmail.com>, Ismael Juma <ismael@juma.me.uk>, Chia-Ping Tsai <chia7712@gmail.com>
This commit is contained in:
TengYao Chi 2025-02-26 05:39:30 +08:00 committed by GitHub
parent fae2e53901
commit 1fed928a0b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 22 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/toc.html
View File

@ -27,7 +27,8 @@
<li><a href="#quickstart">1.3 Quick Start</a>
<li><a href="#ecosystem">1.4 Ecosystem</a>
<li><a href="#upgrade">1.5 Upgrading</a>
<li><a href="#docker">1.6 Docker</a>
<li><a href="/{{version}}/zk2kraft">1.6 Differences Between KRaft mode and ZooKeeper mode</a>
<li><a href="#docker">1.7 Docker</a>
</ul>
<li><a href="#api">2. APIs</a>

3
docs/upgrade.html
View File

@ -61,8 +61,7 @@
Apache Kafka 4.0 only supports KRaft mode - ZooKeeper mode has been removed. As such, broker upgrades to 4.0.x (and higher) require KRaft mode and
the software and metadata versions must be at least 3.3.x (the first version when KRaft mode was deemed production ready). For clusters in KRaft mode
with versions older than 3.3.x, we recommend upgrading to 3.9.x before upgrading to 4.0.x. Clusters in ZooKeeper mode
have to be migrated to KRaft mode before they can be upgraded to 4.0.x as described below.
<!--#include virtual="zk2kraft.html" -->
have to be <a href="/39/documentation.html#kraft_zk_migration">migrated to KRaft mode</a> before they can be upgraded to 4.0.x.
</li>
<li>
Apache Kafka 4.0 ships with a brand-new group coordinator implementation (See <a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=217387038#KIP848:TheNextGenerationoftheConsumerRebalanceProtocol-GroupCoordinator">here</a>.

31
docs/zk2kraft.html
View File

@ -15,14 +15,19 @@
limitations under the License.
-->
<script><!--#include virtual="js/templateData.js" --></script>
<script id="zk2kraft-template" type="text/x-handlebars-template"></script>
<!--#include virtual="../includes/_header.htm" -->
<!--#include virtual="../includes/_top.htm" -->
<div class="content">
<div class="p-zk2kraft">
<h4 class="anchor-heading">Significant Changes in Kafka 4.0 Release</h4>
<p>The following are some of the updates in Kafka 4.0 release:</p>
<h5 class="anchor-heading">Removal Zookeeper configs</h5>
<h1>Differences Between KRaft mode and ZooKeeper mode</h1>
<h2 class="anchor-heading">Removed ZooKeeper Features</h2>
<p>
This section documents differences in behavior between KRaft mode and ZooKeeper mode.
Specifically, several configurations, metrics and features have changed or are no longer required in KRaft mode.
To migrate an existing cluster from ZooKeeper mode to KRaft mode, please refer to the
<a href="/39/documentation.html#kraft_zk_migration">ZooKeeper to KRaft Migration</a> section.
</p>
<h3 class="anchor-heading">Configurations</h3>
<ul>
<li>
<p>
@ -40,7 +45,7 @@
<li><code>password.encoder.iterations</code></li>
</ul>
<p>
In Kraft mode, Kafka stores sensitive data in records, and the data is not encrypted in Kafka.
In KRaft mode, Kafka stores sensitive data in records, and the data is not encrypted in Kafka.
</p>
</li>
<li>
@ -88,7 +93,7 @@
<li><code>broker.id.generation.enable</code></li>
</ul>
<p>
Kafka use the node id in Kraft mode to identify servers.
Kafka use the node id in KRaft mode to identify servers.
</p>
<ul>
<li><code>node.id</code></li>
@ -123,7 +128,7 @@
</li>
<li>
<p>
Removed Zookeeper related configurations.
Removed ZooKeeper related configurations.
</p>
<ul>
<li><code>zookeeper.connect</code></li>
@ -148,7 +153,7 @@
</ul>
</li>
</ul>
<h5 class="anchor-heading">Removal metrics</h5>
<h2 class="anchor-heading">Metrics</h2>
<ul>
<li>
<p>
@ -162,7 +167,7 @@
<li><code>ControlPlaneExpiredConnectionsKilledCount</code></li>
</ul>
<p>
In Kraft mode, Kafka also provides metrics to monitor the network processors and expired connections.
In KRaft mode, Kafka also provides metrics to monitor the network processors and expired connections.
Use the following metrics to monitor the network processors and expired connections:
</p>
<ul>
@ -228,3 +233,5 @@
</li>
</ul>
</div>
<!--#include virtual="../includes/_footer.htm" -->
</div>