This is an automated email from the ASF dual-hosted git repository.
chia7712 pushed a commit to branch 3.9
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/3.9 by this push:
new a2c8823cfe5 MINOR: fix docs references to missing features that are no
longer missing (#20435)
a2c8823cfe5 is described below
commit a2c8823cfe52c7ebc9938618657aa5eee96b4b3b
Author: Chang-Chi Hsu <jim0987795...@gmail.com>
AuthorDate: Wed Sep 3 19:40:58 2025 +0200
MINOR: fix docs references to missing features that are no longer missing
(#20435)
**Changes:**
- Remove outdated "missing features" references from docs
- Updated ZooKeeper deprecation note to clarify removal in Kafka 4.0.
Reviewers: Chia-Ping Tsai <chia7...@gmail.com>
---
docs/ops.html | 16 +---------------
docs/toc.html | 1 -
2 files changed, 1 insertion(+), 16 deletions(-)
diff --git a/docs/ops.html b/docs/ops.html
index 6a2de5f68b8..e8309187a56 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -3731,10 +3731,7 @@ customized state stores; for built-in state stores,
currently we have:
The current stable branch is 3.8. Kafka is regularly updated to include the
latest release in the 3.8 series.
<h4 class="anchor-heading"><a id="zk_depr" class="anchor-link"></a><a
href="#zk_depr">ZooKeeper Deprecation</a></h4>
- <p>With the release of Apache Kafka 3.5, Zookeeper is now marked deprecated.
Removal of ZooKeeper is planned in the next major release of Apache Kafka
(version 4.0),
- which is scheduled to happen no sooner than April 2024. During the
deprecation phase, ZooKeeper is still supported for metadata management of
Kafka clusters,
- but it is not recommended for new deployments. There is a small subset of
features that remain to be implemented in KRaft
- see <a href="#kraft_missing">current missing features</a> for more
information.</p>
+ <p>ZooKeeper mode was deprecated in Apache Kafka 3.5. Apache Kafka version
4.0 removed support for ZooKeeper mode.</p>
<h5 class="anchor-heading"><a id="zk_depr_migration"
class="anchor-link"></a><a href="#zk_drep_migration">Migration</a></h5>
<p>Users are recommended to begin planning for migration to KRaft and also
begin testing to provide any feedback. Refer to <a
href="#kraft_zk_migration">ZooKeeper to KRaft Migration</a> for details on how
to perform a live migration from ZooKeeper to KRaft and current limitations.</p>
@@ -3967,15 +3964,6 @@ foo
<li>The Kafka controllers store all the metadata for the cluster in memory
and on disk. We believe that for a typical Kafka cluster 5GB of main memory and
5GB of disk space on the metadata log director is sufficient.</li>
</ul>
- <h4 class="anchor-heading"><a id="kraft_missing" class="anchor-link"></a><a
href="#kraft_missing">Missing Features</a></h4>
-
- <p>The following features are not fully implemented in KRaft mode:</p>
-
- <ul>
- <li>Supporting JBOD configurations with multiple storage directories. Note
that an Early Access release is supported in 3.7 as per <a
href="https://cwiki.apache.org/confluence/display/KAFKA/KIP-858%3A+Handle+JBOD+broker+disk+failure+in+KRaft";>KIP-858</a>.
Note that it is not yet recommended for use in production environments. Please
refer to the <a
href="https://cwiki.apache.org/confluence/display/KAFKA/Kafka+JBOD+in+KRaft+Early+Access+Release+Notes";>release
notes</a> to help us test [...]
- <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>
<h3>Terminology</h3>
@@ -4008,8 +3996,6 @@ foo
Brokers with broken log directories will only be able to migrate to
KRaft once the directories are repaired.
For further details refer to <a
href="https://issues.apache.org/jira/browse/KAFKA-16431";>KAFKA-16431</a>.
</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>
<li>
There is a known inconsistency between ZK and KRaft modes in the
arguments passed to an <code>AlterConfigPolicy</code>,
when an <code>OpType.SUBTRACT</code> is processed.
diff --git a/docs/toc.html b/docs/toc.html
index c05de6d17f0..f203974dc08 100644
--- a/docs/toc.html
+++ b/docs/toc.html
@@ -175,7 +175,6 @@
<li><a href="#kraft_storage">Storage Tool</a>
<li><a href="#kraft_debug">Debugging</a>
<li><a href="#kraft_deployment">Deploying
Considerations</a>
- <li><a href="#kraft_missing">Missing Features</a>
<li><a href="#kraft_zk_migration">ZooKeeper to KRaft
Migration</a>
</ul>
