(kafka-site) branch markdown updated: KAFKA-19988 Use --cluster instead of -t in one doc example (#760)

[da...@apache.org]

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

davidarthur pushed a commit to branch markdown
in repository https://gitbox.apache.org/repos/asf/kafka-site.git


The following commit(s) were added to refs/heads/markdown by this push:
     new f14965db6 KAFKA-19988 Use --cluster instead of -t in one doc example (#760)
f14965db6 is described below

commit f14965db6285ede7eca7a5363b87b76b25576b45
Author: Gergely Harmadas <54...@users.noreply.github.com>
AuthorDate: Tue Dec 23 03:27:30 2025 +0100

    KAFKA-19988 Use --cluster instead of -t in one doc example (#760)
    
    Slightly change example kafka-storage command in the migration section to account for zookeeper based cluster ids with a leading dash
    
    Reviewers: David Arthur <mu...@gmail.com>
---
 content/en/39/operations/kraft.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/39/operations/kraft.md b/content/en/39/operations/kraft.md
index e0159f8ad..160be09e5 100644
--- a/content/en/39/operations/kraft.md
+++ b/content/en/39/operations/kraft.md
@@ -326,7 +326,7 @@ Follow these steps to format and start a new standalone controller:
     
     
     # Save the previously retrieved cluster ID from ZooKeeper in a variable called zk-cluster-id
-    $ bin/kafka-storage.sh format --standalone -t <zk-cluster-id> -c config/kraft/controller.properties
+    $ bin/kafka-storage.sh format --standalone --cluster-id=<zk-cluster-id> -c config/kraft/controller.properties
     $ bin/kafka-server-start.sh config/kraft/controller.properties
 
 Note: The migration can stall if the ZooKeeper Security Migration Tool was previously executed (see [KAFKA-19480](https://issues.apache.org/jira/browse/KAFKA-19480) for more details). As a workaround, the malformed "/migration" node can be removed from ZooKeeper by running `delete /migration` with the `zookeeper-shell.sh` CLI tool.