This is an automated email from the ASF dual-hosted git repository.
jsancio 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 bb0921865d3 KAFKA-18330: Update documentation to remove controller
deployment limitations (#18281)
bb0921865d3 is described below
commit bb0921865d364737b2b22328c0f891cae4ce6ce8
Author: TengYao Chi <kiting...@gmail.com>
AuthorDate: Wed Jan 15 05:31:16 2025 +0800
KAFKA-18330: Update documentation to remove controller deployment
limitations (#18281)
Reviewers: José Armando García Sancio <jsan...@apache.org>
---
docs/ops.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/ops.html b/docs/ops.html
index 9c7d2bc9e27..e79a8a9581d 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -3963,7 +3963,7 @@ foo
<ul>
<li>Kafka server's <code>process.role</code> should be set to either
<code>broker</code> or <code>controller</code> but not both. Combined mode can
be used in development environments, but it should be avoided in critical
deployment environments.</li>
- <li>For redundancy, a Kafka cluster should use 3 controllers. More than 3
controllers is not recommended in critical environments. In the rare case of a
partial network failure it is possible for the cluster metadata quorum to
become unavailable. This limitation will be addressed in a future release of
Kafka.</li>
+ <li>For redundancy, a Kafka cluster should use 3 or more controllers,
depending on factors like cost and the number of concurrent failures your
system should withstand without availability impact. For the KRaft controller
cluster to withstand <code>N</code> concurrent failures the controller cluster
must include <code>2N + 1</code> controllers.</li>
<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>
