How to Temporarily Shut Down/Stop for Maintenance a TiDB Cluster Deployed on k8s

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: k8s 部署 TiDB 集群如何临时关机/停机维护

| username: TiDBer_hf1k4gsi

[TiDB Usage Environment] Production Environment
[TiDB Version] 6.5.2
[Reproduction Path]
[Encountered Problem] We deployed the TiDB cluster using k8s and now need to upgrade the server configuration (all workers), requiring temporary shutdown for maintenance (permission to shut down external services has been granted). The forum suggests using TiUP to shut down the cluster, but how should we handle it since we used the operator for deployment? Should we delete the tc resources to let the operator delete each component, then add them back after restarting the machines? Or can I directly restart the machines?
[Resource Configuration] 3 masters, 3 workers

2
| username: tidb菜鸟一只 | Original post link

Suspend the cluster using TiDB Operator,

3
| username: liuis | Original post link

Upgrade all workers at once? Can’t they be evicted and upgraded one by one?

4
| username: yiduoyunQ | Original post link

Offline: The above suspend document is supported starting from v1.4.0
Online:
image

5
| username: TiDBer_hf1k4gsi | Original post link

So it’s called “suspend” here. No wonder I couldn’t find any results when searching for “shutdown” or “stop”.

6
| username: TiDBer_hf1k4gsi | Original post link

Applied for downtime maintenance, it needs to be done one machine at a time. Waiting for data range migration back and forth is even more troublesome.

7
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.