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

dajac 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 0da509c11 Update doc for 4.0-rc3
0da509c11 is described below

commit 0da509c11edd8e65fdb86e68bbc5eaffd12205eb
Author: David Jacot <[email protected]>
AuthorDate: Sat Mar 8 09:38:30 2025 +0100

    Update doc for 4.0-rc3
---
 40/upgrade.html  |  4 ++--
 40/zk2kraft.html | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 64 insertions(+), 3 deletions(-)

diff --git a/40/upgrade.html b/40/upgrade.html
index 8b90d8f82..5d3d6caec 100644
--- a/40/upgrade.html
+++ b/40/upgrade.html
@@ -27,9 +27,9 @@
     <li>Upgrade the brokers one at a time: shut down the broker, update the 
code, and restart it. Once you have done so, the
         brokers will be running the latest version and you can verify that the 
cluster's behavior and performance meets expectations.
     </li>
-    <li>Once the cluster's behavior and performance has been verified, bump 
the metadata.version by running
+    <li>Once the cluster's behavior and performance has been verified, 
finalize the upgrade by running
         <code>
-            bin/kafka-features.sh upgrade --metadata 4.0
+            bin/kafka-features.sh --bootstrap-server localhost:9092 upgrade 
--release-version 4.0
         </code>
     </li>
     <li>Note that cluster metadata downgrade is not supported in this version 
since it has metadata changes.
diff --git a/40/zk2kraft.html b/40/zk2kraft.html
index f2df5505a..ae7c7ff1b 100644
--- a/40/zk2kraft.html
+++ b/40/zk2kraft.html
@@ -153,6 +153,67 @@
             </ul>
         </li>
     </ul>
+    <h3 class="anchor-heading">Dynamic Log Levels</h3>
+    <ul>
+        <li>
+            <p>
+                The dynamic log levels feature allows you to change the log4j 
settings of a running broker or controller process without restarting it. The 
command-line syntax for setting dynamic log levels on brokers has not changed 
in KRaft mode. Here is an example of setting the log level on a broker:<br/>
+                <pre><code class="language-bash">
+./bin/kafka-configs.sh --bootstrap-server localhost:9092 \
+    --entity-type broker-loggers \
+    --entity-name 1 \
+    --alter \
+    --add-config org.apache.kafka.raft.KafkaNetworkChannel=TRACE
+                </code></pre>
+            </p>
+        </li>
+        <li>
+            <p>
+                When setting dynamic log levels on the controllers, the 
<code>--bootstrap-controller</code> flag must be used. Here is an example of 
setting the log level ona  controller:<br/>
+                <pre><code class="language-bash">
+./bin/kafka-configs.sh --bootstrap-controller localhost:9093 \
+    --entity-type broker-loggers \
+    --entity-name 1 \
+    --alter \
+    --add-config org.apache.kafka.raft.KafkaNetworkChannel=TRACE
+                </code></pre><br/>
+                Note that the entity-type must be specified as 
<code>broker-loggers</code>, even though we are changing a controller&#39;s log 
level rather than a broker&#39;s log level.
+            </p>
+        </li>
+        <li>
+            <p>
+                When changing the log level of a combined node, which has both 
broker and controller roles, either --bootstrap-servers or 
--bootstrap-controllers may be used. Combined nodes have only a single set of 
log levels&#59; there are not different log levels for the broker and 
controller parts of the process.
+            </p>
+        </li>
+    </ul>
+    <h3 class="anchor-heading">Dynamic Controller Configurations</h3>
+    <ul>
+        <li>
+            <p>
+                Some Kafka configurations can be changed dynamically, without 
restarting the process.  The command-line syntax for setting dynamic log levels 
on brokers has not changed in KRaft mode. Here is an example of setting the 
number of IO threads on a broker:<br/>
+                <pre><code class="language-bash">
+./bin/kafka-configs.sh --bootstrap-server localhost:9092 \
+    --entity-type brokers \
+    --entity-name 1 \
+    --alter \
+    --add-config num.io.threads=5
+                </code></pre>
+            </p>
+        </li>
+        <li>
+            <p>
+                Controllers will apply all applicable cluster-level dynamic 
configurations. For example, the following command-line will change the 
<code>max.connections</code> setting on all of the brokers and all of the 
controllers in the cluster:<br/>
+                <pre><code class="language-bash">
+./bin/kafka-configs.sh --bootstrap-server localhost:9092 \
+    --entity-type brokers \
+    --entity-default \
+    --alter \
+    --add-config max.connections=10000
+                </code></pre><br/>
+                It is not currently possible to apply a dynamic configuration 
on only a single controller.
+            </p>
+        </li>
+    </ul>
     <h2 class="anchor-heading">Metrics</h2>
     <ul>
         <li>
@@ -256,4 +317,4 @@
     </ul>
 </div>
 <!--#include virtual="../includes/_footer.htm" -->
-</div>
\ No newline at end of file
+</div>

Reply via email to