This is an automated email from the ASF dual-hosted git repository.
chia7712 pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/kafka-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new fc52e3a6d KAFKA-18330 Update documentation to remove controller
deployment limitations (#659)
fc52e3a6d is described below
commit fc52e3a6def4fd0bd480420c7acffd3f926de8a1
Author: TengYao Chi <[email protected]>
AuthorDate: Tue Feb 25 18:01:24 2025 +0800
KAFKA-18330 Update documentation to remove controller deployment
limitations (#659)
Reviewers: Chia-Ping Tsai <[email protected]>
---
39/ops.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/39/ops.html b/39/ops.html
index 912a3408e..9908bb5c1 100644
--- a/39/ops.html
+++ b/39/ops.html
@@ -3962,7 +3962,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>
