Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: TIDB集群断电问题咨询
【TiDB Usage Environment】Production Environment
【TiDB Version】
【Encountered Problem】
Hello teachers, recently a switch in our server room had an issue, and now we need to replace the switch (the switch where the TiDB cluster is located). During the switch replacement, there will be a network outage, and the entire TiDB cluster will be disconnected (for about 10-20 minutes). I would like to ask what impact this operation will have on TiDB? What should we pay attention to? Do we need to make any pre-configurations (like timeout settings, liveness detection time, etc.) for the cluster? Thank you~~
In this scenario, it’s a matter of shutting down for maintenance. Just stop the entire cluster first.
Consider getting a UPS for the switch… 
If it exceeds half an hour, the Raft version basically can’t catch up and will evolve into catching up with the snapshot version. After reaching a certain level of alignment, it will catch up to the Raft log.
During this period, the cluster may be inaccessible or extremely slow to access…
Isn’t UPS a backup power supply? This is not a question, we are replacing the switch.
In our situation, wouldn’t we need a hot standby switch to avoid affecting the business?
Yes, a backup power supply, a small one, should be enough to last for a few hours.
Shut down the cluster: tiup cluster stop ${cluster-name}
Start the cluster after replacement: tiup cluster start ${cluster-name}
Teacher, is there anything wrong with the above operations?
Yes, it’s these two commands
Shut down the entire cluster, that’s the safest way.
I haven’t encountered this kind of problem before. I have encountered situations where TiKV was taken offline and deleted.
It’s better to make a backup before shutting down, just in case.
Physical backups are fast, while logical backups are better for restoring individual tables.
This topic was automatically closed 1 minute after the last reply. No new replies are allowed.
|
username: jaybing926
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: