(kafka) branch 4.0 updated: KAFKA-18330: Update documentation to remove controller deployment limitations (#18281)

[js...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jsancio pushed a commit to branch 4.0
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/4.0 by this push:
     new a0a43430120 KAFKA-18330: Update documentation to remove controller deployment limitations (#18281)
a0a43430120 is described below

commit a0a43430120c93d8a2e2753a24aa3f70645c7e72
Author: TengYao Chi <ki...@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 <js...@apache.org>
---
 docs/ops.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/ops.html b/docs/ops.html
index 2b8ad0c8bfb..8849c5e2163 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -3857,7 +3857,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 or 5 controllers, depending on factors like cost and the number of concurrent failures your system should withstand without availability impact. 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>