Five TiKV nodes were forcibly taken offline by operations

Translated
1

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

Original topic: 被运维强制下线了5台tikv

| username: tidb狂热爱好者

【TiDB Usage Environment】Test Environment
【TiDB Version】6.0
【Encountered Issue】
【Reproduction Path】What operations were performed to cause the issue
【Problem Phenomenon and Impact】

  • Getting system info of 172.31.177.212:37254 … Done
  • Getting system info of 172.31.177.210:37254 … Done
  • Getting system info of 172.31.177.214:37254 … Done
  • Getting system info of 172.31.177.215:37254 … Done
  • Getting system info of 172.31.177.216:37254 … Done
  • Getting system info of 172.31.177.151:37254 … Error
  • Getting system info of 172.31.177.153:37254 … Error
  • Getting system info of 172.31.177.154:37254 … Error
  • Getting system info of 172.31.177.150:37254 … Error
  • Getting system info of 172.31.177.152:37254 … Error
  • Getting system info of 172.31.177.213:37254 … Done
    【Attachments】

Please provide the version information of each component, such as cdc/tikv, which can be obtained by executing cdc version/tikv-server --version.

2
| username: tidb狂热爱好者 | Original post link

The data cannot be recovered, and these TiKV nodes need to be forcibly taken offline.

3
| username: tidb狂热爱好者 | Original post link

Could you please help answer this question?

4
| username: Kongdom | Original post link

You can scale down these five machines using the scale-down command.

5
| username: tidb狂热爱好者 | Original post link

Okay, I’ll try it first. Scale down.

6
| username: system | Original post link

This topic was automatically closed 1 minute after the last reply. No new replies are allowed.