fix: update commands for mentactl (#1155)

Author: everpcpc

docs/cn/guides/10-deploy/01-deploy/02-production/30-metasrv-backup-restore.md

@@ -1,8 +1,7 @@
 ---
 title: 备份和恢复 Databend 元服务集群
 sidebar_label: 备份和恢复元服务
-description:
-  如何备份和恢复元服务集群数据
+description: 如何备份和恢复元服务集群数据
 ---
 
 本指南将介绍如何备份和恢复元服务集群数据。
@@ -17,7 +16,7 @@ description:
 其中 `<ip:port>` 是 [databend-meta.toml](https://github.com/datafuselabs/databend/blob/main/scripts/distribution/configs/databend-meta.toml) 中的 `grpc_api_address`，例如：
 
 ```shell
-databend-metactl --export --grpc-api-address "127.0.0.1:9191" --db <output_fn>
+databend-metactl export --grpc-api-address "127.0.0.1:9191" --db <output_fn>
 
 # tail "<output_fn>"
 # ["state_machine/0",{"Nodes":{"key":2,"value":{"name":"","endpoint":{"addr":"localhost","port":28203}}}}]
@@ -33,7 +32,7 @@ databend-metactl --export --grpc-api-address "127.0.0.1:9191" --db <output_fn>
 
 ```sh
 
-databend-metactl --export --raft-dir "<your_meta_dir>" --db <output_fn>
+databend-metactl export --raft-dir "<your_meta_dir>" --db <output_fn>
 
 # tail "<output_fn>"
 # ["state_machine/0",{"Nodes":{"key":2,"value":{"name":"","endpoint":{"addr":"localhost","port":28203}}}}]
@@ -50,15 +49,15 @@ databend-metactl --export --raft-dir "<your_meta_dir>" --db <output_fn>
 以下命令从导出的元数据中在 `<your_meta_dir>` 重建一个元服务数据库：
 
 ```sh
-databend-metactl --import --raft-dir "<your_meta_dir>" --db <output_fn>
+databend-metactl import --raft-dir "<your_meta_dir>" --db <output_fn>
 
 databend-meta --raft-dir "<your_meta_dir>" ...
 ```
 
 注意：如果没有 `--db` 参数，导入的数据将来自标准输入，如：
 
 ```sh
-cat "<output_fn>" | databend-metactl --import --raft-dir "<your_meta_dir>"
+cat "<output_fn>" | databend-metactl import --raft-dir "<your_meta_dir>"
 ```
 
 **注意**：`<your_meta_dir>` 中的数据将被清除。
@@ -71,9 +70,9 @@ cat "<output_fn>" | databend-metactl --import --raft-dir "<your_meta_dir>"
 例如：
 
 ```
-databend-metactl --import --raft-dir ./.databend/new_meta1 --id=1 --db meta.db --initial-cluster 1=localhost:29103 --initial-cluster 2=localhost:29203 --initial-cluster 3=localhost:29303
-databend-metactl --import --raft-dir ./.databend/new_meta2 --id=2 --db meta.db --initial-cluster 1=localhost:29103 --initial-cluster 2=localhost:29203 --initial-cluster 3=localhost:29303
-databend-metactl --import --raft-dir ./.databend/new_meta3 --id=3 --db meta.db --initial-cluster 1=localhost:29103 --initial-cluster 2=localhost:29203 --initial-cluster 3=localhost:29303
+databend-metactl import --raft-dir ./.databend/new_meta1 --id=1 --db meta.db --initial-cluster 1=localhost:29103 --initial-cluster 2=localhost:29203 --initial-cluster 3=localhost:29303
+databend-metactl import --raft-dir ./.databend/new_meta2 --id=2 --db meta.db --initial-cluster 1=localhost:29103 --initial-cluster 2=localhost:29203 --initial-cluster 3=localhost:29303
+databend-metactl import --raft-dir ./.databend/new_meta3 --id=3 --db meta.db --initial-cluster 1=localhost:29103 --initial-cluster 2=localhost:29203 --initial-cluster 3=localhost:29303
 ```
 
 上述脚本从 `meta.db` 导入导出的数据，并初始化三个集群节点：id 1，其 raft 目录为 `./.databend/new_meta1`，id 2 和 3 也是如此，但使用不同的 raft 目录。

docs/en/guides/10-deploy/01-deploy/02-production/30-metasrv-backup-restore.md

@@ -1,8 +1,7 @@
 ---
 title: Back Up and Restore Databend Meta Service Cluster
 sidebar_label: Backup and Restore Meta Service
-description:
-  How to back up and restore Meta Service cluster data
+description: How to back up and restore Meta Service cluster data
 ---
 
 This guideline will introduce how to back up and restore the meta service cluster data.
@@ -17,7 +16,7 @@ Similar to exporting from data dir, but with the service endpoint argument `--gr
 where `<ip:port>` is the `grpc_api_address` in [databend-meta.toml](https://github.com/datafuselabs/databend/blob/main/scripts/distribution/configs/databend-meta.toml), e.g.:
 
 ```shell
-databend-metactl --export --grpc-api-address "127.0.0.1:9191" --db <output_fn>
+databend-metactl export --grpc-api-address "127.0.0.1:9191" --db <output_fn>
 
 # tail "<output_fn>"
 # ["state_machine/0",{"Nodes":{"key":2,"value":{"name":"","endpoint":{"addr":"localhost","port":28203}}}}]
@@ -33,7 +32,7 @@ E.g., every line in the output file is a JSON of an exported key-value record.
 
 ```sh
 
-databend-metactl --export --raft-dir "<your_meta_dir>" --db <output_fn>
+databend-metactl export --raft-dir "<your_meta_dir>" --db <output_fn>
 
 # tail "<output_fn>"
 # ["state_machine/0",{"Nodes":{"key":2,"value":{"name":"","endpoint":{"addr":"localhost","port":28203}}}}]
@@ -51,15 +50,15 @@ The following command rebuild a meta service db in `<your_meta_dir>` from
 exported metadata:
 
 ```sh
-databend-metactl --import --raft-dir "<your_meta_dir>" --db <output_fn>
+databend-metactl import --raft-dir "<your_meta_dir>" --db <output_fn>
 
 databend-meta --raft-dir "<your_meta_dir>" ...
 ```
 
 Note: without the `--db` argument, the import data come from stdio instead, like:
 
 ```sh
-cat "<output_fn>" | databend-metactl --import --raft-dir "<your_meta_dir>"
+cat "<output_fn>" | databend-metactl import --raft-dir "<your_meta_dir>"
 ```
 
 **Caveat**: Data in `<your_meta_dir>` will be cleared.
@@ -72,9 +71,9 @@ The `--initial-cluster` format is: `node_id=raft_advertise_host:raft_api_port`,
 E.g.:
 
 ```
-databend-metactl --import --raft-dir ./.databend/new_meta1 --id=1 --db meta.db --initial-cluster 1=localhost:29103 --initial-cluster 2=localhost:29203 --initial-cluster 3=localhost:29303
-databend-metactl --import --raft-dir ./.databend/new_meta2 --id=2 --db meta.db --initial-cluster 1=localhost:29103 --initial-cluster 2=localhost:29203 --initial-cluster 3=localhost:29303
-databend-metactl --import --raft-dir ./.databend/new_meta3 --id=3 --db meta.db --initial-cluster 1=localhost:29103 --initial-cluster 2=localhost:29203 --initial-cluster 3=localhost:29303
+databend-metactl import --raft-dir ./.databend/new_meta1 --id=1 --db meta.db --initial-cluster 1=localhost:29103 --initial-cluster 2=localhost:29203 --initial-cluster 3=localhost:29303
+databend-metactl import --raft-dir ./.databend/new_meta2 --id=2 --db meta.db --initial-cluster 1=localhost:29103 --initial-cluster 2=localhost:29203 --initial-cluster 3=localhost:29303
+databend-metactl import --raft-dir ./.databend/new_meta3 --id=3 --db meta.db --initial-cluster 1=localhost:29103 --initial-cluster 2=localhost:29203 --initial-cluster 3=localhost:29303
 ```
 
 The script above imports the exported data from `meta.db` and initializes the three cluster nodes: id 1, which raft directory is `./.databend/new_meta1`, and so are id 2 and 3 with different raft directory.

docs/en/guides/10-deploy/01-deploy/02-production/60-metasrv-status.md

@@ -1,8 +1,7 @@
 ---
 title: Meta Service HTTP APIs
 sidebar_label: Meta Service HTTP APIs
-description:
-  Meta Service HTTP APIs
+description: Meta Service HTTP APIs
 ---
 
 In order to capture and keep track of various meta stats that are useful for your analysis, Databend provides a number of HTTP APIs.
@@ -78,6 +77,12 @@ Returns the status information of each meta node in the cluster.
 }
 ```
 
+### MetaCTL command
+
+```shell
+databend-metactl status
+```
+
 ## Meta Metrics API
 
 Shows a bunch of metrics that Databend captures and tracks about the meta service performance. For more information about the meta service metrics, see [Databend Meta Metrics](../../03-monitor/10-metasrv-metrics.md).