From 59c15069e65f1e7f3ae18b16d6e93ff0bfe1d08f Mon Sep 17 00:00:00 2001 From: Ran Date: Mon, 3 Jul 2023 09:49:46 +0800 Subject: [PATCH] Update ticdc/ticdc-faq.md Co-authored-by: Grace Cai --- ticdc/ticdc-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ticdc/ticdc-faq.md b/ticdc/ticdc-faq.md index 96e54f387cd66..571422a95e4ca 100644 --- a/ticdc/ticdc-faq.md +++ b/ticdc/ticdc-faq.md @@ -287,7 +287,7 @@ TiDB has a transaction timeout mechanism. When a transaction runs for a period l ## Why can't I use the `cdc cli` command to operate a TiCDC cluster deployed by TiDB Operator? -This is because the default port number of the TiCDC cluster deployed by TiDB Operator is 8301, while the default port number of the `cdc cli` command to connect to the TiCDC server is 8300. When using the cdc cli command to operate the TiCDC cluster deployed by TiDB Operator, you need to explicitly specify the `--server` parameter, as follows: +This is because the default port number of the TiCDC cluster deployed by TiDB Operator is `8301`, while the default port number of the `cdc cli` command to connect to the TiCDC server is `8300`. When using the `cdc cli` command to operate the TiCDC cluster deployed by TiDB Operator, you need to explicitly specify the `--server` parameter, as follows: ```shell ./cdc cli changefeed list --server "127.0.0.1:8301"