This is an automated email from the ASF dual-hosted git repository.
viktor 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 da6d33ec2 KAFKA-19480: Add workaround for hanging kraft migration due
to null /migration znode (#708)
da6d33ec2 is described below
commit da6d33ec2141cc701be4f453c2a95ef3b9694f5b
Author: Gergely Harmadas <[email protected]>
AuthorDate: Tue Oct 7 12:14:17 2025 +0200
KAFKA-19480: Add workaround for hanging kraft migration due to null
/migration znode (#708)
---
34/ops.html | 2 ++
35/ops.html | 2 ++
36/ops.html | 2 ++
37/ops.html | 2 ++
38/ops.html | 2 ++
39/ops.html | 2 ++
6 files changed, 12 insertions(+)
diff --git a/34/ops.html b/34/ops.html
index 4e590e6b1..b8db9bd92 100644
--- a/34/ops.html
+++ b/34/ops.html
@@ -3685,6 +3685,8 @@ zookeeper.connect=localhost:2181
# Other configs ...</pre>
+ <p>Note: The migration can stall if the <a
href="#zk_authz_migration">ZooKeeper Security Migration Tool</a> was previously
executed (see <a
href="https://issues.apache.org/jira/browse/KAFKA-19480";>KAFKA-19026</a> for
more details). As a workaround, the malformed "/migration" node can be removed
from ZooKeeper by running <code>delete /migration</code> with the
<code>zookeeper-shell.sh</code> CLI tool.</p>
+
<p><em>Note: The KRaft cluster <code>node.id</code> values must be different
from any existing ZK broker <code>broker.id</code>.
In KRaft-mode, the brokers and controllers share the same Node ID
namespace.</em></p>
diff --git a/35/ops.html b/35/ops.html
index 44ade2529..27257f8cb 100644
--- a/35/ops.html
+++ b/35/ops.html
@@ -3704,6 +3704,8 @@ zookeeper.connect=localhost:2181
# Other configs ...</pre>
+ <p>Note: The migration can stall if the <a
href="#zk_authz_migration">ZooKeeper Security Migration Tool</a> was previously
executed (see <a
href="https://issues.apache.org/jira/browse/KAFKA-19480";>KAFKA-19026</a> for
more details). As a workaround, the malformed "/migration" node can be removed
from ZooKeeper by running <code>delete /migration</code> with the
<code>zookeeper-shell.sh</code> CLI tool.</p>
+
<p><em>Note: The KRaft cluster <code>node.id</code> values must be different
from any existing ZK broker <code>broker.id</code>.
In KRaft-mode, the brokers and controllers share the same Node ID
namespace.</em></p>
diff --git a/36/ops.html b/36/ops.html
index 133b48ee1..66436ad92 100644
--- a/36/ops.html
+++ b/36/ops.html
@@ -3852,6 +3852,8 @@ zookeeper.connect=localhost:2181
# Other configs ...</pre>
+ <p>Note: The migration can stall if the <a
href="#zk_authz_migration">ZooKeeper Security Migration Tool</a> was previously
executed (see <a
href="https://issues.apache.org/jira/browse/KAFKA-19480";>KAFKA-19026</a> for
more details). As a workaround, the malformed "/migration" node can be removed
from ZooKeeper by running <code>delete /migration</code> with the
<code>zookeeper-shell.sh</code> CLI tool.</p>
+
<p><em>Note: The KRaft cluster <code>node.id</code> values must be different
from any existing ZK broker <code>broker.id</code>.
In KRaft-mode, the brokers and controllers share the same Node ID
namespace.</em></p>
diff --git a/37/ops.html b/37/ops.html
index 73a192a18..5dfed7968 100644
--- a/37/ops.html
+++ b/37/ops.html
@@ -3928,6 +3928,8 @@ inter.broker.listener.name=PLAINTEXT
# Other configs ...</pre>
+ <p>Note: The migration can stall if the <a
href="#zk_authz_migration">ZooKeeper Security Migration Tool</a> was previously
executed (see <a
href="https://issues.apache.org/jira/browse/KAFKA-19480";>KAFKA-19026</a> for
more details). As a workaround, the malformed "/migration" node can be removed
from ZooKeeper by running <code>delete /migration</code> with the
<code>zookeeper-shell.sh</code> CLI tool.</p>
+
<p><em>Note: The KRaft cluster <code>node.id</code> values must be different
from any existing ZK broker <code>broker.id</code>.
In KRaft-mode, the brokers and controllers share the same Node ID
namespace.</em></p>
diff --git a/38/ops.html b/38/ops.html
index 27666303c..2c75f0e88 100644
--- a/38/ops.html
+++ b/38/ops.html
@@ -3933,6 +3933,8 @@ inter.broker.listener.name=PLAINTEXT
# Other configs ...</code></pre>
+ <p>Note: The migration can stall if the <a
href="#zk_authz_migration">ZooKeeper Security Migration Tool</a> was previously
executed (see <a
href="https://issues.apache.org/jira/browse/KAFKA-19480";>KAFKA-19026</a> for
more details). As a workaround, the malformed "/migration" node can be removed
from ZooKeeper by running <code>delete /migration</code> with the
<code>zookeeper-shell.sh</code> CLI tool.</p>
+
<p><em>Note: The KRaft cluster <code>node.id</code> values must be different
from any existing ZK broker <code>broker.id</code>.
In KRaft-mode, the brokers and controllers share the same Node ID
namespace.</em></p>
diff --git a/39/ops.html b/39/ops.html
index 646d1c3ca..076ec20a3 100644
--- a/39/ops.html
+++ b/39/ops.html
@@ -4083,6 +4083,8 @@ inter.broker.listener.name=PLAINTEXT
$ bin/kafka-storage.sh format --standalone -t <zk-cluster-id> -c
config/kraft/controller.properties
$ bin/kafka-server-start.sh config/kraft/controller.properties</code></pre>
+ <p>Note: The migration can stall if the <a
href="#zk_authz_migration">ZooKeeper Security Migration Tool</a> was previously
executed (see <a
href="https://issues.apache.org/jira/browse/KAFKA-19480";>KAFKA-19026</a> for
more details). As a workaround, the malformed "/migration" node can be removed
from ZooKeeper by running <code>delete /migration</code> with the
<code>zookeeper-shell.sh</code> CLI tool.</p>
+
<p><em>Note: The KRaft cluster <code>node.id</code> values must be different
from any existing ZK broker <code>broker.id</code>.
In KRaft-mode, the brokers and controllers share the same Node ID
namespace.</em></p>
