Skip to content

Commit e395eed

Browse files
authored
tiup: add description in tiup upgrade doc (#2368) (#2393)
1 parent 5a456c8 commit e395eed

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

how-to/upgrade/using-tiup.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,11 @@ This section describes how to perform a rolling update to the TiDB cluster and h
148148
tiup cluster upgrade <cluster-name> v4.0.0-rc
149149
```
150150

151-
Performing the rolling update to the cluster will update all components one by one. During the upgrade of TiKV, all leaders in a TiKV instance are evicted before stopping the instance. The default timeout time is 10 minutes. The instance is directly stopped after this timeout time.
151+
Performing the rolling update to the cluster will update all components one by one. During the upgrade of TiKV, all leaders in a TiKV instance are evicted before stopping the instance. The default timeout time is 5 minutes. The instance is directly stopped after this timeout time.
152+
153+
To perform the upgrade immediately without evicting the leader, specify `--force` in the command above. This method causes performance jitter but not data loss.
154+
155+
To keep a stable performance, make sure that all leaders in a TiKV instance are evicted before stopping the instance. You can set `--transfer-timeout` to a super large value, for example, `--transfer-timeout 100000000` (unit: second).
152156

153157
### Verify the cluster version
154158

0 commit comments

Comments
 (0)