Skip to content

Commit 9b8a16a

Browse files
everpcpceverpcpc
authored
fix: change port to default (#2437)
1 parent feebafe commit 9b8a16a

File tree

16 files changed

+51
-51
lines changed

16 files changed

+51
-51
lines changed

‎docs/cn/guides/10-deploy/01-deploy/02-production/10-metasrv-deploy.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ cd configs && nano databend-meta.toml
6262

6363
```toml title="databend-meta.toml"
6464
log_dir = "/var/log/databend"
65-
admin_api_address = "0.0.0.0:28101"
65+
admin_api_address = "0.0.0.0:28002"
6666
grpc_api_address = "0.0.0.0:9191"
6767
# databend-query fetch this address to update its databend-meta endpoints list,
6868
# in case databend-meta cluster changes.
@@ -87,7 +87,7 @@ single = true
8787

8888
```toml title="databend-meta.toml"
8989
log_dir = "/var/log/databend"
90-
admin_api_address = "0.0.0.0:28101"
90+
admin_api_address = "0.0.0.0:28002"
9191
grpc_api_address = "0.0.0.0:9191"
9292
# databend-query fetch this address to update its databend-meta endpoints list,
9393
# in case databend-meta cluster changes.
@@ -113,7 +113,7 @@ join = ["172.16.125.128:28103", "172.16.125.130:28103"]
113113

114114
```toml title="databend-meta.toml"
115115
log_dir = "/var/log/databend"
116-
admin_api_address = "0.0.0.0:28101"
116+
admin_api_address = "0.0.0.0:28002"
117117
grpc_api_address = "0.0.0.0:9191"
118118
# databend-query fetch this address to update its databend-meta endpoints list,
119119
# in case databend-meta cluster changes.
@@ -147,7 +147,7 @@ cd .. && cd bin
147147
3. 启动所有 meta 节点后，您可以使用以下 curl 命令检查它们：
148148

149149
```shell
150-
curl 172.16.125.128:28101/v1/cluster/nodes
150+
curl 172.16.125.128:28002/v1/cluster/nodes
151151
[{"name":"1","endpoint":{"addr":"172.16.125.128","port":28103},"grpc_api_advertise_address":"172.16.125.128:9191"},{"name":"2","endpoint":{"addr":"172.16.125.129","port":28103},"grpc_api_advertise_address":"172.16.125.129:9191"},{"name":"3","endpoint":{"addr":"172.16.125.130","port":28103},"grpc_api_advertise_address":"172.16.125.130:9191"}]
152152
```
153153

@@ -236,8 +236,8 @@ FROM
236236
┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
237237
│ name │ cluster │ host │ port │ version │
238238
├────────────────────────┼─────────┼────────────────┼────────┼─────────────────────────────────────────────────────────────────────────┤
239-
│ 7rwadq5otY2AlBDdT25QL4 │ default │ 172.16.125.132 │ 9091 │ v1.2.410-4b8cd16f0c(rust-1.77.0-nightly-2024-04-08T12:21:53.785045868Z) │
240-
│ cH331pYsoFmvMSZXKRrn2 │ default │ 172.16.125.131 │ 9091 │ v1.2.410-4b8cd16f0c(rust-1.77.0-nightly-2024-04-08T12:21:53.785045868Z) │
239+
│ 7rwadq5otY2AlBDdT25QL4 │ default │ 172.16.125.132 │ 9090 │ v1.2.410-4b8cd16f0c(rust-1.77.0-nightly-2024-04-08T12:21:53.785045868Z) │
240+
│ cH331pYsoFmvMSZXKRrn2 │ default │ 172.16.125.131 │ 9090 │ v1.2.410-4b8cd16f0c(rust-1.77.0-nightly-2024-04-08T12:21:53.785045868Z) │
241241
└──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
242242
2 rows read in 0.031 sec. Processed 2 rows, 327 B (64.1 rows/s, 10.23 KiB/s)
243243
```
@@ -251,4 +251,4 @@ FROM
251251

252252
<!-- <LanguageFileParse
253253
cn={<VideoCN />}
254-
/> -->
254+
/> -->

‎docs/cn/guides/10-deploy/01-deploy/02-production/20-metasrv-add-remove-node.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ raft_dir = "metadata/datas7"
3131
raft_api_port = 28703
3232
raft_listen_host = "127.0.0.1"
3333
raft_advertise_host = "localhost"
34-
join = ["localhost:28103"]
34+
join = ["localhost:28004"]
3535
```
3636

3737
参数 `join` 指定要加入的现有集群中节点的 raft 地址列表 (`<raft_advertise_host>:<raft_api_port>`)。
@@ -80,15 +80,15 @@ join = ["localhost:28103"]
8080
在添加或删除节点的每个步骤中，都应检查集群状态，以确保一切顺利。
8181

8282
在配置中定义的 `admin-api-address` 提供了一个管理 HTTP 服务来检查集群状态：
83-
例如，`curl -s localhost:28101/v1/cluster/nodes` 将显示集群中的成员：
83+
例如，`curl -s localhost:28002/v1/cluster/nodes` 将显示集群中的成员：
8484

8585
```json
8686
[
8787
{
8888
"name": "1",
8989
"endpoint": {
9090
"addr": "localhost",
91-
"port": 28103
91+
"port": 28004
9292
}
9393
},
9494
{
@@ -99,4 +99,4 @@ join = ["localhost:28103"]
9999
}
100100
}
101101
]
102-
```
102+
```

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ description: Meta Service HTTP APIs
77
为了捕获和跟踪各种对您的分析有用的元数据统计信息，Databend 提供了许多 HTTP API。
88

99
:::note
10-
除非另有说明，否则这些 HTTP API 默认使用端口 `28101`。要更改默认端口，请编辑配置文件 `databend-meta.toml` 中的 `admin_api_address` 值。
10+
除非另有说明，否则这些 HTTP API 默认使用端口 `28002`。要更改默认端口，请编辑配置文件 `databend-meta.toml` 中的 `admin_api_address` 值。
1111
:::
1212

1313
## Cluster Node API
@@ -24,7 +24,7 @@ description: Meta Service HTTP APIs
2424
[
2525
{
2626
name: "1",
27-
endpoint: { addr: "localhost", port: 28103 },
27+
endpoint: { addr: "localhost", port: 28004 },
2828
grpc_api_addr: "0.0.0.0:9191",
2929
},
3030
{
@@ -48,7 +48,7 @@ description: Meta Service HTTP APIs
4848
```json
4949
{
5050
"id": 1,
51-
"endpoint": "localhost:28103",
51+
"endpoint": "localhost:28004",
5252
"db_size": 18899209,
5353
"state": "Follower",
5454
"is_leader": false,
@@ -63,7 +63,7 @@ description: Meta Service HTTP APIs
6363
"voters": [
6464
{
6565
"name": "1",
66-
"endpoint": { "addr": "localhost", "port": 28103 },
66+
"endpoint": { "addr": "localhost", "port": 28004 },
6767
"grpc_api_addr": "0.0.0.0:9191"
6868
},
6969
{

‎docs/cn/guides/10-deploy/03-monitor/10-metasrv-metrics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Metrics are crucial to monitor the performance and health of the system. Databen
88

99
你可以通过 Web 浏览器使用以下 URL 访问 metrics：
1010

11-
- Meta Metrics: `http://<admin_api_address>/v1/metrics`. 默认为 `0.0.0.0:28101/v1/metrics`.
11+
- Meta Metrics: `http://<admin_api_address>/v1/metrics`. 默认为 `0.0.0.0:28002/v1/metrics`.
1212
- Query Metrics: `http://<metric_api_address>/metrics`. 默认为 `0.0.0.0:7070/metrics`.
1313

1414
:::tip

‎docs/cn/guides/10-deploy/03-monitor/tools/prometheus-and-grafana.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ title: Prometheus & Grafana
1313
按照[部署指南](/guides/deploy)部署本地 Databend。
1414

1515
:::tip
16-
本教程使用安装包 `configs` 文件夹中的[默认配置文件](https://github.com/databendlabs/databend/tree/main/scripts/distribution/configs)。databend-meta 的 metrics API 是 `0.0.0.0:28101/v1/metrics`，databend-query 的 metrics API 是 `0.0.0.0:7070/metrics`。
16+
本教程使用安装包 `configs` 文件夹中的[默认配置文件](https://github.com/databendlabs/databend/tree/main/scripts/distribution/configs)。databend-meta 的 metrics API 是 `0.0.0.0:28002/v1/metrics`，databend-query 的 metrics API 是 `0.0.0.0:7070/metrics`。
1717
:::
1818

1919
### 步骤 2. 部署 Prometheus
@@ -49,7 +49,7 @@ title: Prometheus & Grafana
4949
# scheme defaults to 'http'.
5050

5151
static_configs:
52-
- targets: ["host.docker.internal:28101"]
52+
- targets: ["host.docker.internal:28002"]
5353
```
5454
5555
3. 部署 Prometheus。
@@ -103,4 +103,4 @@ title: Prometheus & Grafana
103103

104104
![Grafana import query json](/img/tracing/grafana-query-json.png)
105105

106-
![Grafana query dashboard](/img/tracing/grafana-query-dashboard.png)
106+
![Grafana query dashboard](/img/tracing/grafana-query-dashboard.png)

‎docs/cn/guides/10-deploy/04-references/02-node-config/01-metasrv-config.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ title: Meta 节点配置
88
# Usage:
99
# databend-meta -c databend-meta.toml
1010

11-
admin_api_address = "0.0.0.0:28101"
11+
admin_api_address = "0.0.0.0:28002"
1212
grpc_api_address = "0.0.0.0:9191"
1313
# databend-query fetch this address to update its databend-meta endpoints list,
1414
# in case databend-meta cluster changes.
@@ -17,7 +17,7 @@ grpc_api_advertise_host = "127.0.0.1"
1717
[raft_config]
1818
id = 1
1919
raft_dir = "/var/lib/databend/raft"
20-
raft_api_port = 28103
20+
raft_api_port = 28004
2121

2222
# Assign raft_{listen|advertise}_host in test config.
2323
# This allows you to catch a bug in unit tests when something goes wrong in raft meta nodes communication.

‎docs/cn/tutorials/recovery/bendsave.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ enable_virtual_host_style = false
106106
启动服务后，通过检查其运行状况端点来验证它们是否正在运行。成功的响应应返回 HTTP 状态 200 OK。
107107

108108
```bash
109-
curl -I http://127.0.0.1:28101/v1/health
109+
curl -I http://127.0.0.1:28002/v1/health
110110

111111
curl -I http://127.0.0.1:8080/v1/health
112112
```
@@ -229,4 +229,4 @@ SELECT * FROM books;
229229
├──────────────────┼──────────────────┼──────────────────┤
230230
│ 1 │ Invisible Stars │ General │
231231
└────────────────────────────────────────────────────────┘
232-
```
232+
```

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

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ root@meta-1:/usr/databend# tar -xzvf databend-v1.2.410-aarch64-unknown-linux-gnu
5151
| raft_listen_host | 172.16.125.128 | 172.16.125.129 | 172.16.125.130 |
5252
| raft_advertise_host | 172.16.125.128 | 172.16.125.129 | 172.16.125.130 |
5353
| single | true | / | / |
54-
| join | / | ["172.16.125.128:28103","172.16.125.130:28103"] | ["172.16.125.128:28103","172.16.125.129:28103"] |
54+
| join | / | ["172.16.125.128:28004","172.16.125.130:28004"] | ["172.16.125.128:28004","172.16.125.129:28004"] |
5555

5656
```shell
5757
cd configs && nano databend-meta.toml
@@ -62,7 +62,7 @@ cd configs && nano databend-meta.toml
6262

6363
```toml title="databend-meta.toml"
6464
log_dir = "/var/log/databend"
65-
admin_api_address = "0.0.0.0:28101"
65+
admin_api_address = "0.0.0.0:28002"
6666
grpc_api_address = "0.0.0.0:9191"
6767
# databend-query fetch this address to update its databend-meta endpoints list,
6868
# in case databend-meta cluster changes.
@@ -71,7 +71,7 @@ grpc_api_advertise_host = "172.16.125.128"
7171
[raft_config]
7272
id = 1
7373
raft_dir = "/var/lib/databend/raft"
74-
raft_api_port = 28103
74+
raft_api_port = 28004
7575

7676
# Assign raft_{listen|advertise}_host in test config.
7777
# This allows you to catch a bug in unit tests when something goes wrong in raft meta nodes communication.
@@ -87,7 +87,7 @@ single = true
8787

8888
```toml title="databend-meta.toml"
8989
log_dir = "/var/log/databend"
90-
admin_api_address = "0.0.0.0:28101"
90+
admin_api_address = "0.0.0.0:28002"
9191
grpc_api_address = "0.0.0.0:9191"
9292
# databend-query fetch this address to update its databend-meta endpoints list,
9393
# in case databend-meta cluster changes.
@@ -96,7 +96,7 @@ grpc_api_advertise_host = "172.16.125.129"
9696
[raft_config]
9797
id = 2
9898
raft_dir = "/var/lib/databend/raft"
99-
raft_api_port = 28103
99+
raft_api_port = 28004
100100

101101
# Assign raft_{listen|advertise}_host in test config.
102102
# This allows you to catch a bug in unit tests when something goes wrong in raft meta nodes communication.
@@ -105,15 +105,15 @@ raft_advertise_host = "172.16.125.129"
105105

106106
# Start up mode: single node cluster
107107
# single = true
108-
join = ["172.16.125.128:28103", "172.16.125.130:28103"]
108+
join = ["172.16.125.128:28004", "172.16.125.130:28004"]
109109
```
110110

111111
</TabItem>
112112
<TabItem value="Meta-3" label="Meta-3">
113113

114114
```toml title="databend-meta.toml"
115115
log_dir = "/var/log/databend"
116-
admin_api_address = "0.0.0.0:28101"
116+
admin_api_address = "0.0.0.0:28002"
117117
grpc_api_address = "0.0.0.0:9191"
118118
# databend-query fetch this address to update its databend-meta endpoints list,
119119
# in case databend-meta cluster changes.
@@ -122,7 +122,7 @@ grpc_api_advertise_host = "172.16.125.130"
122122
[raft_config]
123123
id = 3
124124
raft_dir = "/var/lib/databend/raft"
125-
raft_api_port = 28103
125+
raft_api_port = 28004
126126

127127
# Assign raft_{listen|advertise}_host in test config.
128128
# This allows you to catch a bug in unit tests when something goes wrong in raft meta nodes communication.
@@ -131,7 +131,7 @@ raft_advertise_host = "172.16.125.130"
131131

132132
# Start up mode: single node cluster
133133
# single = true
134-
join = ["172.16.125.128:28103", "172.16.125.129:28103"]
134+
join = ["172.16.125.128:28004", "172.16.125.129:28004"]
135135
```
136136

137137
</TabItem>
@@ -147,8 +147,8 @@ cd .. && cd bin
147147
3. Once all the meta nodes have started, you can check them using the following curl command:
148148

149149
```shell
150-
curl 172.16.125.128:28101/v1/cluster/nodes
151-
[{"name":"1","endpoint":{"addr":"172.16.125.128","port":28103},"grpc_api_advertise_address":"172.16.125.128:9191"},{"name":"2","endpoint":{"addr":"172.16.125.129","port":28103},"grpc_api_advertise_address":"172.16.125.129:9191"},{"name":"3","endpoint":{"addr":"172.16.125.130","port":28103},"grpc_api_advertise_address":"172.16.125.130:9191"}]
150+
curl 172.16.125.128:28002/v1/cluster/nodes
151+
[{"name":"1","endpoint":{"addr":"172.16.125.128","port":28004},"grpc_api_advertise_address":"172.16.125.128:9191"},{"name":"2","endpoint":{"addr":"172.16.125.129","port":28004},"grpc_api_advertise_address":"172.16.125.129:9191"},{"name":"3","endpoint":{"addr":"172.16.125.130","port":28004},"grpc_api_advertise_address":"172.16.125.130:9191"}]
152152
```
153153

154154
## Step 2: Deploy Query Nodes
@@ -235,8 +235,8 @@ FROM
235235
┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
236236
│ name │ cluster │ host │ port │ version │
237237
├────────────────────────┼─────────┼────────────────┼────────┼─────────────────────────────────────────────────────────────────────────┤
238-
│ 7rwadq5otY2AlBDdT25QL4 │ default │ 172.16.125.132 │ 9091 │ v1.2.410-4b8cd16f0c(rust-1.77.0-nightly-2024-04-08T12:21:53.785045868Z) │
239-
│ cH331pYsoFmvMSZXKRrn2 │ default │ 172.16.125.131 │ 9091 │ v1.2.410-4b8cd16f0c(rust-1.77.0-nightly-2024-04-08T12:21:53.785045868Z) │
238+
│ 7rwadq5otY2AlBDdT25QL4 │ default │ 172.16.125.132 │ 9090 │ v1.2.410-4b8cd16f0c(rust-1.77.0-nightly-2024-04-08T12:21:53.785045868Z) │
239+
│ cH331pYsoFmvMSZXKRrn2 │ default │ 172.16.125.131 │ 9090 │ v1.2.410-4b8cd16f0c(rust-1.77.0-nightly-2024-04-08T12:21:53.785045868Z) │
240240
└──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
241241
2 rows read in 0.031 sec. Processed 2 rows, 327 B (64.1 rows/s, 10.23 KiB/s)
242242
```

‎docs/en/guides/10-deploy/01-deploy/02-production/20-metasrv-add-remove-node.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ raft_dir = "metadata/datas7"
3131
raft_api_port = 28703
3232
raft_listen_host = "127.0.0.1"
3333
raft_advertise_host = "localhost"
34-
join = ["localhost:28103"]
34+
join = ["localhost:28004"]
3535
```
3636

3737
The arg `join` specifies a list of raft addresses(`<raft_advertise_host>:<raft_api_port>`) of nodes in the existing cluster it wants to
@@ -86,15 +86,15 @@ As part of the command, the node will be blocked from interacting with the clust
8686
At every step of adding or removing a node, the cluster state should be checked to ensure everything goes well.
8787

8888
The `admin-api-address` defined in the config provides a administration HTTP service to examine cluster state:
89-
E.g., `curl -s localhost:28101/v1/cluster/nodes` will display the members in a cluster:
89+
E.g., `curl -s localhost:28002/v1/cluster/nodes` will display the members in a cluster:
9090

9191
```json
9292
[
9393
{
9494
"name": "1",
9595
"endpoint": {
9696
"addr": "localhost",
97-
"port": 28103
97+
"port": 28004
9898
}
9999
},
100100
{

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ description: Meta Service HTTP APIs
77
In order to capture and keep track of various meta stats that are useful for your analysis, Databend provides a number of HTTP APIs.
88

99
:::note
10-
Unless otherwise specified, these HTTP APIs use the port `28101` by default. To change the default port, edit the value of `admin_api_address` in the configuration file `databend-meta.toml`.
10+
Unless otherwise specified, these HTTP APIs use the port `28002` by default. To change the default port, edit the value of `admin_api_address` in the configuration file `databend-meta.toml`.
1111
:::
1212

1313
## Cluster Node API
@@ -24,7 +24,7 @@ Returns all the meta nodes in the cluster.
2424
[
2525
{
2626
name: "1",
27-
endpoint: { addr: "localhost", port: 28103 },
27+
endpoint: { addr: "localhost", port: 28004 },
2828
grpc_api_addr: "0.0.0.0:9191",
2929
},
3030
{
@@ -48,7 +48,7 @@ Returns the status information of each meta node in the cluster.
4848
```json
4949
{
5050
"id": 1,
51-
"endpoint": "localhost:28103",
51+
"endpoint": "localhost:28004",
5252
"db_size": 18899209,
5353
"state": "Follower",
5454
"is_leader": false,
@@ -63,7 +63,7 @@ Returns the status information of each meta node in the cluster.
6363
"voters": [
6464
{
6565
"name": "1",
66-
"endpoint": { "addr": "localhost", "port": 28103 },
66+
"endpoint": { "addr": "localhost", "port": 28004 },
6767
"grpc_api_addr": "0.0.0.0:9191"
6868
},
6969
{

‎docs/en/guides/10-deploy/03-monitor/10-metasrv-metrics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Metrics are crucial to monitor the performance and health of the system. Databen
88

99
You can access the metrics through a web browser using the following URLs:
1010

11-
- Meta Metrics: `http://<admin_api_address>/v1/metrics`. Defaults to `0.0.0.0:28101/v1/metrics`.
11+
- Meta Metrics: `http://<admin_api_address>/v1/metrics`. Defaults to `0.0.0.0:28002/v1/metrics`.
1212
- Query Metrics: `http://<metric_api_address>/metrics`. Defaults to `0.0.0.0:7070/metrics`.
1313

1414
:::tip

‎docs/en/guides/10-deploy/03-monitor/tools/prometheus-and-grafana.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ This following tutorial guides you through deploying and integrating Databend, P
1313
Follow the [Deployment Guide](/guides/deploy) to deploy a local Databend.
1414

1515
:::tip
16-
This tutorial uses the [default configuration files](https://github.com/databendlabs/databend/tree/main/scripts/distribution/configs) in the `configs` folder of the install package. The metrics API for databend-meta is `0.0.0.0:28101/v1/metrics`, and the metrics API for databend-query is `0.0.0.0:7070/metrics`.
16+
This tutorial uses the [default configuration files](https://github.com/databendlabs/databend/tree/main/scripts/distribution/configs) in the `configs` folder of the install package. The metrics API for databend-meta is `0.0.0.0:28002/v1/metrics`, and the metrics API for databend-query is `0.0.0.0:7070/metrics`.
1717
:::
1818

1919
### Step 2. Deploy Prometheus
@@ -49,7 +49,7 @@ The steps below describe how to install and deploy Prometheus using Docker.
4949
# scheme defaults to 'http'.
5050

5151
static_configs:
52-
- targets: ["host.docker.internal:28101"]
52+
- targets: ["host.docker.internal:28002"]
5353
```
5454
5555
3. Deploy Prometheus.

0 commit comments

Comments
 (0)