You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by gi...@apache.org on 2026/05/14 03:10:56 UTC
(kafka-site) branch asf-staging updated: Updated asf-staging from GHA workflow run 25839302527
This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/kafka-site.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new d2a51944f5 Updated asf-staging from GHA workflow run 25839302527
d2a51944f5 is described below
commit d2a51944f5c87ddfcf49945c3e4f8b8f46408916
Author: github-actions[bot] <41...@users.noreply.github.com>
AuthorDate: Thu May 14 03:10:50 2026 +0000
Updated asf-staging from GHA workflow run 25839302527
Commit: https://github.com/apache/kafka-site/commit/a04884cbee149139b0e8220c7de19107bb3f195f
GitHub Run: https://github.com/apache/kafka-site/actions/runs/25839302527
---
39/_print/index.html | 4 ++--
39/operations/_print/index.html | 4 ++--
39/operations/kraft/index.html | 6 +++---
sitemap.xml | 2 +-
4 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/39/_print/index.html b/39/_print/index.html
index 4863a2c93e..cd60768312 100644
--- a/39/_print/index.html
+++ b/39/_print/index.html
@@ -5877,7 +5877,7 @@ foo
"partitionEpoch" : 0
}
>> exit
-</code></pre><h2 id=deploying-considerations>Deploying Considerations<a class=td-heading-self-link href=#deploying-considerations aria-label="Heading self-link"></a></h2><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 more cont [...]
+</code></pre><h2 id=deploying-considerations>Deploying Considerations<a class=td-heading-self-link href=#deploying-considerations aria-label="Heading self-link"></a></h2><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 more cont [...]
</code></pre><p>It is generally useful to enable DEBUG logging on the KRaft controllers and the ZK brokers during the migration.</p><h3 id=provisioning-the-kraft-controller-quorum>Provisioning the KRaft controller quorum<a class=td-heading-self-link href=#provisioning-the-kraft-controller-quorum aria-label="Heading self-link"></a></h3><p>Two things are needed before the migration can begin. First, the brokers must be configured to support the migration and second, a KRaft controller quor [...]
</code></pre><p>The KRaft controller quorum should also be provisioned with the latest <code>metadata.version</code>. This is done automatically when you format the node with the <code>kafka-storage.sh</code> tool. For further instructions on KRaft deployment, please refer to the above documentation.</p><p>In addition to the standard KRaft configuration, the KRaft controllers will need to enable support for the migration as well as provide ZooKeeper connection configuration.</p><p>Here i [...]
process.roles=controller
@@ -5951,7 +5951,7 @@ listeners=CONTROLLER://:9093
# zookeeper.connect=localhost:2181
# Other configs ...
-</code></pre><h3 id=reverting-to-zookeeper-mode-during-the-migration>Reverting to ZooKeeper mode During the Migration<a class=td-heading-self-link href=#reverting-to-zookeeper-mode-during-the-migration aria-label="Heading self-link"></a></h3><p>While the cluster is still in migration mode, it is possible to revert to ZooKeeper mode. The process to follow depends on how far the migration has progressed. In order to find out how to revert, select the <strong>final</strong> migration step t [...]
+</code></pre><h3 id=reverting-to-zookeeper-mode-during-the-migration>Reverting to ZooKeeper mode During the Migration<a class=td-heading-self-link href=#reverting-to-zookeeper-mode-during-the-migration aria-label="Heading self-link"></a></h3><p>While the cluster is still in migration mode, it is possible to revert to ZooKeeper mode. The process to follow depends on how far the migration has progressed. In order to find out how to revert, select the <strong>final</strong> migration step t [...]
# ex: `git checkout 3.9.1`
$ ./gradlew clean :storage:testJar
</code></pre><p>After build successfully, there should be a <code>kafka-storage-x.x.x-test.jar</code> file under <code>storage/build/libs</code>. Next, setting configurations in the broker side to enable tiered storage feature.</p><pre><code># Sample Zookeeper/Kraft broker server.properties listening on PLAINTEXT://:9092
diff --git a/39/operations/_print/index.html b/39/operations/_print/index.html
index 9ce2505bb1..cf63bb0423 100644
--- a/39/operations/_print/index.html
+++ b/39/operations/_print/index.html
@@ -427,7 +427,7 @@ foo
"partitionEpoch" : 0
}
>> exit
-</code></pre><h2 id=deploying-considerations>Deploying Considerations<a class=td-heading-self-link href=#deploying-considerations aria-label="Heading self-link"></a></h2><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 more cont [...]
+</code></pre><h2 id=deploying-considerations>Deploying Considerations<a class=td-heading-self-link href=#deploying-considerations aria-label="Heading self-link"></a></h2><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 more cont [...]
</code></pre><p>It is generally useful to enable DEBUG logging on the KRaft controllers and the ZK brokers during the migration.</p><h3 id=provisioning-the-kraft-controller-quorum>Provisioning the KRaft controller quorum<a class=td-heading-self-link href=#provisioning-the-kraft-controller-quorum aria-label="Heading self-link"></a></h3><p>Two things are needed before the migration can begin. First, the brokers must be configured to support the migration and second, a KRaft controller quor [...]
</code></pre><p>The KRaft controller quorum should also be provisioned with the latest <code>metadata.version</code>. This is done automatically when you format the node with the <code>kafka-storage.sh</code> tool. For further instructions on KRaft deployment, please refer to the above documentation.</p><p>In addition to the standard KRaft configuration, the KRaft controllers will need to enable support for the migration as well as provide ZooKeeper connection configuration.</p><p>Here i [...]
process.roles=controller
@@ -501,7 +501,7 @@ listeners=CONTROLLER://:9093
# zookeeper.connect=localhost:2181
# Other configs ...
-</code></pre><h3 id=reverting-to-zookeeper-mode-during-the-migration>Reverting to ZooKeeper mode During the Migration<a class=td-heading-self-link href=#reverting-to-zookeeper-mode-during-the-migration aria-label="Heading self-link"></a></h3><p>While the cluster is still in migration mode, it is possible to revert to ZooKeeper mode. The process to follow depends on how far the migration has progressed. In order to find out how to revert, select the <strong>final</strong> migration step t [...]
+</code></pre><h3 id=reverting-to-zookeeper-mode-during-the-migration>Reverting to ZooKeeper mode During the Migration<a class=td-heading-self-link href=#reverting-to-zookeeper-mode-during-the-migration aria-label="Heading self-link"></a></h3><p>While the cluster is still in migration mode, it is possible to revert to ZooKeeper mode. The process to follow depends on how far the migration has progressed. In order to find out how to revert, select the <strong>final</strong> migration step t [...]
# ex: `git checkout 3.9.1`
$ ./gradlew clean :storage:testJar
</code></pre><p>After build successfully, there should be a <code>kafka-storage-x.x.x-test.jar</code> file under <code>storage/build/libs</code>. Next, setting configurations in the broker side to enable tiered storage feature.</p><pre><code># Sample Zookeeper/Kraft broker server.properties listening on PLAINTEXT://:9092
diff --git a/39/operations/kraft/index.html b/39/operations/kraft/index.html
index cd7deb6a63..abcb787364 100644
--- a/39/operations/kraft/index.html
+++ b/39/operations/kraft/index.html
@@ -1,5 +1,5 @@
<!doctype html><html itemscope itemtype=http://schema.org/WebPage lang=en class=no-js><head><meta charset=utf-8><meta name=viewport content="width=device-width,initial-scale=1,shrink-to-fit=no"><meta name=robots content="index, follow"><link rel=icon type=image/png sizes=32x32 href=/images/apache.png><link rel=icon type=image/png sizes=16x16 href=/images/apache.png><link rel="shortcut icon" href=/images/apache.png><link rel=apple-touch-icon sizes=180x180 href=/images/apache.png><title>KR [...]
-<meta name=description content="KRaft"><meta property="og:title" content="KRaft"><meta property="og:description" content="KRaft"><meta property="og:type" content="article"><meta property="og:url" content="https://kafka.apache.org/39/operations/kraft/"><meta property="article:section" content="39"><meta property="article:modified_time" content="2026-02-22T20:11:19+09:00"><meta itemprop=name content="KRaft"><meta itemprop=description content="KRaft"><meta itemprop=dateModified content="202 [...]
+<meta name=description content="KRaft"><meta property="og:title" content="KRaft"><meta property="og:description" content="KRaft"><meta property="og:type" content="article"><meta property="og:url" content="https://kafka.apache.org/39/operations/kraft/"><meta property="article:section" content="39"><meta property="article:modified_time" content="2026-05-14T04:08:11+01:00"><meta itemprop=name content="KRaft"><meta itemprop=description content="KRaft"><meta itemprop=dateModified content="202 [...]
<span></span>
<span></span></div></button>
<a class="navbar-brand order-1 order-lg-0 mx-auto mx-lg-0" href=/><img src=/logos/kafka_logo--simple.png alt="Apache Kafka" class=navbar-logo-img></a><div class="order-2 d-lg-none" style=width:48px></div><div class="collapse navbar-collapse order-3 order-lg-1" id=main_navbar><ul class="navbar-nav ms-auto"><li class="nav-item dropdown"><a class="nav-link dropdown-toggle" href=/42/getting-started/ aria-haspopup=true aria-expanded=false>Get Started</a><ul class=dropdown-menu><li><a class=dr [...]
@@ -147,7 +147,7 @@ foo
"partitionEpoch" : 0
}
>> exit
-</code></pre><h2 id=deploying-considerations>Deploying Considerations<a class=td-heading-self-link href=#deploying-considerations aria-label="Heading self-link"></a></h2><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 more cont [...]
+</code></pre><h2 id=deploying-considerations>Deploying Considerations<a class=td-heading-self-link href=#deploying-considerations aria-label="Heading self-link"></a></h2><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 more cont [...]
</code></pre><p>It is generally useful to enable DEBUG logging on the KRaft controllers and the ZK brokers during the migration.</p><h3 id=provisioning-the-kraft-controller-quorum>Provisioning the KRaft controller quorum<a class=td-heading-self-link href=#provisioning-the-kraft-controller-quorum aria-label="Heading self-link"></a></h3><p>Two things are needed before the migration can begin. First, the brokers must be configured to support the migration and second, a KRaft controller quor [...]
</code></pre><p>The KRaft controller quorum should also be provisioned with the latest <code>metadata.version</code>. This is done automatically when you format the node with the <code>kafka-storage.sh</code> tool. For further instructions on KRaft deployment, please refer to the above documentation.</p><p>In addition to the standard KRaft configuration, the KRaft controllers will need to enable support for the migration as well as provide ZooKeeper connection configuration.</p><p>Here i [...]
process.roles=controller
@@ -221,7 +221,7 @@ listeners=CONTROLLER://:9093
# zookeeper.connect=localhost:2181
# Other configs ...
-</code></pre><h3 id=reverting-to-zookeeper-mode-during-the-migration>Reverting to ZooKeeper mode During the Migration<a class=td-heading-self-link href=#reverting-to-zookeeper-mode-during-the-migration aria-label="Heading self-link"></a></h3><p>While the cluster is still in migration mode, it is possible to revert to ZooKeeper mode. The process to follow depends on how far the migration has progressed. In order to find out how to revert, select the <strong>final</strong> migration step t [...]
+</code></pre><h3 id=reverting-to-zookeeper-mode-during-the-migration>Reverting to ZooKeeper mode During the Migration<a class=td-heading-self-link href=#reverting-to-zookeeper-mode-during-the-migration aria-label="Heading self-link"></a></h3><p>While the cluster is still in migration mode, it is possible to revert to ZooKeeper mode. The process to follow depends on how far the migration has progressed. In order to find out how to revert, select the <strong>final</strong> migration step t [...]
<span class="text-dark text-truncate d-inline-block" style=max-width:18rem>ZooKeeper</span></a></div><div class="ms-auto d-flex flex-column align-items-end"><a class="btn pager-btn rounded-3 fw-semibold py-2 px-3 d-inline-flex align-items-center gap-2" style=min-width:12rem href=/39/operations/tiered-storage/ rel=next aria-label="Next: Tiered Storage"><span class="fw-semibold text-dark">Next:</span>
<span class="text-dark text-truncate d-inline-block text-end" style=max-width:18rem>Tiered Storage
</span><span class="fw-semibold text-dark">›</span></a></div></nav></div></main></div></div><footer class="td-footer d-print-none"><div class=container-fluid><div class="row align-items-center"><div class="col-12 col-md-3 text-center text-md-start"><div class=td-footer__social-icons><a href=/community/contact/ target=_blank rel=noopener aria-label=Contact class=td-footer__social-link><i class="fa fa-envelope"></i>
diff --git a/sitemap.xml b/sitemap.xml
index 1f69a46e17..a149cca19c 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>https://kafka.apache.org/0100/implementation/api-design/</loc><lastmod>2025-12-19T18:23:57-08:00</lastmod></url><url><loc>https://kafka.apache.org/0101/implementation/api-design/</loc><lastmod>2025-12-19T18:23:57-08:00</lastmod></url><url><loc>https://kafka.apache.org/0102/implementation/api-design/</loc><lastmod>2025-12-1 [...]
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>https://kafka.apache.org/0100/implementation/api-design/</loc><lastmod>2025-12-19T18:23:57-08:00</lastmod></url><url><loc>https://kafka.apache.org/0101/implementation/api-design/</loc><lastmod>2025-12-19T18:23:57-08:00</lastmod></url><url><loc>https://kafka.apache.org/0102/implementation/api-design/</loc><lastmod>2025-12-1 [...]
\ No newline at end of file