This is an automated email from the ASF dual-hosted git repository.
chia7712 pushed a commit to branch 3.9
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/3.9 by this push:
new 2795198aa8f MINOR: Correct JIRA issue link in ops.html (#20682)
2795198aa8f is described below
commit 2795198aa8fd9b428f9b9e467aa9af58bc4c27b7
Author: Lan Ding <[email protected]>
AuthorDate: Sat Oct 11 01:15:28 2025 +0800
MINOR: Correct JIRA issue link in ops.html (#20682)
see https://github.com/apache/kafka/pull/20627#discussion_r2413728286
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]>
---
docs/ops.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/ops.html b/docs/ops.html
index bbcb194c245..838271c4d91 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -4048,7 +4048,7 @@ inter.broker.listener.name=PLAINTEXT
<p>The new standalone controller in the example configuration above should
be formatted using the <code>kafka-storage format
--standalone</code>command.</p>
- <p>Note: The migration can stall if the <a
href="#zk_authz_migration">ZooKeeper Security Migration Tool</a> was previously
executed (fixed from 3.9.2, 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 (fixed from 3.9.2, 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>
