You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: maintain-tidb-using-tiup.md
+46-2Lines changed: 46 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,7 @@ When the cluster is in operation, if you need to modify the parameters of a comp
110
110
log.slow-threshold: 300
111
111
```
112
112
113
-
For the parameter format, see the [TiUP parameter template](https://github.com/pingcap-incubator/tiup-cluster/blob/master/examples/topology.example.yaml).
113
+
For the parameter format, see the [TiUP parameter template](https://github.com/pingcap/tiup/blob/master/examples/topology.example.yaml).
114
114
115
115
**Use `.` to represent the hierarchy of the configuration items**.
116
116
@@ -134,7 +134,51 @@ server_configs:
134
134
performance.txn-total-size-limit: 1073741824
135
135
```
136
136
137
-
Then run the `tiup cluster reload ${cluster-name} -N tidb`command to rolling restart the TiDB component.
137
+
Then, run the `tiup cluster reload ${cluster-name} -R tidb`command to rolling restart the TiDB component.
138
+
139
+
## Replace with a hotfix package
140
+
141
+
For normal upgrade, see [Upgrade TiDB Using TiUP](/upgrade-tidb-using-tiup.md). But in some scenarios, such as debugging, you might need to replace the currently running component with a temporary package. To achieve this, use the `patch` command:
142
+
143
+
{{< copyable "shell-root">}}
144
+
145
+
```bash
146
+
tiup cluster patch --help
147
+
```
148
+
149
+
```
150
+
Replace the remote package with a specified package and restart the service
0 commit comments