Skip to content

Commit 937f9de

Browse files
authored
Introduce how to deploy on arm64 (pingcap#4091)
1 parent d5106aa commit 937f9de

File tree

1 file changed

+17
-1
lines changed

1 file changed

+17
-1
lines changed

tiup/tiup-cluster.md

+17-1
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,22 @@ monitoring_servers:
9999
- host: 172.16.5.134
100100
```
101101
102+
By default, TiUP is deployed as the binary files running on the amd64 architecture. If the target machine is the arm64 architecture, you can configure it in the topology file:
103+
104+
```yaml
105+
global:
106+
arch: "arm64" # Configures all machines to use the binary files of the arm64 architecture by default
107+
108+
tidb_servers:
109+
- host: 172.16.5.134
110+
arch: "amd64" # Configures this machine to use the binary files of the amd64 architecture
111+
- host: 172.16.5.139
112+
arch: "arm64" # Configures this machine to use the binary files of the arm64 architecture
113+
- host: 172.16.5.140 # Machines that are not configured with the arch field use the default value in the global field, which is arm64 in this case.
114+
115+
...
116+
```
117+
102118
Save the file as `/tmp/topology.yaml`. If you want to use TiDB v3.0.12 and your cluster name is `prod-cluster`, run the following command:
103119

104120
{{< copyable "shell-regular" >}}
@@ -128,7 +144,7 @@ prometheus 172.16.5.134 9090 deploy/prometheus-9090,data/prometheus-90
128144
grafana 172.16.5.134 3000 deploy/grafana-3000
129145
Attention:
130146
1. If the topology is not what you expected, check your yaml file.
131-
1. Please confirm there is no port/directory conflicts in same host.
147+
2. Please confirm there is no port/directory conflicts in same host.
132148
Do you want to continue? [y/N]:
133149
```
134150

0 commit comments

Comments
 (0)