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 95d129686 MINOR: Correct JIRA issue link in ops.html (#730)
95d129686 is described below
commit 95d1296867443dc5611cb4976b8d9f7db9451697
Author: Lan Ding <[email protected]>
AuthorDate: Mon Oct 13 21:50:06 2025 +0800
MINOR: Correct JIRA issue link in ops.html (#730)
see apache/kafka#20627 (comment)
This pull request corrects a typo in the documentation by updating the JIRA
link from KAFKA-19026 to KAFKA-19480 in the ops.html file.
Reviewers: Chia-Ping Tsai [email protected]
---
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, 6 insertions(+), 6 deletions(-)
diff --git a/34/ops.html b/34/ops.html
index b8db9bd92..f76609df6 100644
--- a/34/ops.html
+++ b/34/ops.html
@@ -3685,7 +3685,7 @@ 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>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-19480</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 27257f8cb..a20b5bdf8 100644
--- a/35/ops.html
+++ b/35/ops.html
@@ -3704,7 +3704,7 @@ 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>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-19480</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 66436ad92..12579a276 100644
--- a/36/ops.html
+++ b/36/ops.html
@@ -3852,7 +3852,7 @@ 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>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-19480</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 5dfed7968..c9ff00aca 100644
--- a/37/ops.html
+++ b/37/ops.html
@@ -3928,7 +3928,7 @@ 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>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-19480</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 2c75f0e88..3c3cdd6b4 100644
--- a/38/ops.html
+++ b/38/ops.html
@@ -3933,7 +3933,7 @@ 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>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-19480</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 076ec20a3..c57d3ff83 100644
--- a/39/ops.html
+++ b/39/ops.html
@@ -4083,7 +4083,7 @@ 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>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-19480</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>
