tidb数据库修改tikv为单副本，解决单机环境下io负载过高的问题

七七powerful2026-08-08 10:48

tidb 安装在单机环境，但使用了3个tikv，iowait 达到80%，cpu 100%

1.查看数据库信息

bash 复制代码 
[sudoroot@ln-server-01 ~]$ tiup cluster list
Checking updates for component cluster... Timedout (after 2s)
Name       User      Version  Path                                                     PrivateKey
----       ----      -------  ----                                                     ----------
xx-tidb  sudoroot  v7.5.1   /home/sudoroot/.tiup/storage/cluster/clusters/xx-tidb  /home/sudoroot/.tiup/storage/cluster/clusters/xx-tidb/ssh/id_rsa
[sudoroot@ln-server-01 ~]$ tiup cluster display xx-tidb
Checking updates for component cluster... Timedout (after 2s)
Cluster type:       tidb
Cluster name:       xx-tidb
Cluster version:    v7.5.1
Deploy user:        sudoroot
SSH type:           builtin
Dashboard URL:      http://10.x.x.211:23380/dashboard
Grafana URL:        http://10.x.x.211:3000
ID                 Role          Host         Ports        OS/Arch       Status  Data Dir                                            Deploy Dir
--                 ----          ----         -----        -------       ------  --------                                            ----------
10.x.x.211:9093   alertmanager  10.x.x.211  9093/9094    linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/alertmanager-90  /opt/tidb/tidb-7.5.1/tidb-deploy/alertmanager-90
10.x.x.211:3000   grafana       10.x.x.211  3000         linux/x86_64  Up      -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/grafana-3000
10.x.x.211:23379  pd            10.x.x.211  23379/24380  linux/x86_64  Up|L    /opt/tidb/tidb-data/tidb/tidb-data/pd-23379         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23379
10.x.x.211:23380  pd            10.x.x.211  23380/24381  linux/x86_64  Up|UI   /opt/tidb/tidb-data/tidb/tidb-data/pd-23380         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23380
10.x.x.211:23381  pd            10.x.x.211  23381/24382  linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/pd-23381         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23381
10.x.x.211:9090   prometheus    10.x.x.211  9090/12020   linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/prometheus-8249  /opt/tidb/tidb-7.5.1/tidb-deploy/prometheus-8249
10.x.x.211:4000   tidb          10.x.x.211  4000/10080   linux/x86_64  Up      -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4000
10.x.x.211:4001   tidb          10.x.x.211  4001/10081   linux/x86_64  Up      -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4001
10.x.x.211:4003   tidb          10.x.x.211  4003/10083   linux/x86_64  Up      -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4003
10.x.x.211:20160  tikv          10.x.x.211  20160/20180  linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/tikv-20160       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20160
10.x.x.211:20161  tikv          10.x.x.211  20161/20181  linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/tikv-20161       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20161
10.x.x.211:20162  tikv          10.x.x.211  20162/20182  linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/tikv-20162       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20162
Total nodes: 12
[sudoroot@ln-server-01 ~]$

2.修改单副本：

bash 复制代码 
[sudoroot@ln-server-01 ~]$ tiup ctl:v7.5.1 pd -i -u http://10.x.x.211:23379
The component `ctl` version v7.5.1 is not installed; downloading from repository.
Starting component ctl: /home/sudoroot/.tiup/components/ctl/v7.5.1/ctl pd -i -u http://10.x.x.211:23379
>> config show replication
{
  "max-replicas": 3,
  "location-labels": "host",
  "strictly-match-label": "false",
  "enable-placement-rules": "true",
  "enable-placement-rules-cache": "false",
  "isolation-level": ""
}

>> config set replication.max-replicas 1
Success!
>> config show replication
{
  "max-replicas": 1,
  "location-labels": "host",
  "strictly-match-label": "false",
  "enable-placement-rules": "true",
  "enable-placement-rules-cache": "false",
  "isolation-level": ""
}

>>

3.登录数据库确认：

校验是否还有 Region 存在多副本：

复制代码 
SELECT region_id,COUNT(DISTINCT store_id) replica_num
FROM information_schema.tikv_region_peers
GROUP BY region_id
HAVING replica_num > 1;
bash 复制代码 
mysql> SELECT region_id,COUNT(DISTINCT store_id) replica_num
    -> FROM information_schema.tikv_region_peers
    -> GROUP BY region_id
    -> HAVING replica_num > 1;
Empty set (0.01 sec)

mysql>

4.缩容tikv，如有需要：

使用 TiUP 扩容缩容 TiDB 集群 | TiDB 社区版TiUP 可以在不中断线上服务的情况下扩容和缩容 TiDB 集群。使用 `tiup cluster list` 查看当前集群名称列表。扩容 TiDB/PD/TiKV 节点需要编写扩容拓扑配置，并执行扩容命令。扩容后，使用 `tiup cluster display ` 检查集群状态。缩容 TiDB/PD/TiKV 节点需要查看节点 ID 信息，执行缩容操作，然后检查集群状态。缩容 TiFlash/TiCDC 节点也需要执行相似的操作。 https://pingkai.cn/docs/tidb/stable/scale-tidb-using-tiup#%E7%BC%A9%E5%AE%B9-tidbpdtikv-%E8%8A%82%E7%82%B9

bash 复制代码 
tiup cluster scale-in xx-tidb --node 10.x.x.211:20161
tiup cluster scale-in xx-tidb --node 10.x.x.211:20162


[sudoroot@ln-server-01 ~]$ tiup cluster display xx-tidb
Checking updates for component cluster... Timedout (after 2s)
Cluster type:       tidb
Cluster name:       xx-tidb
Cluster version:    v7.5.1
Deploy user:        sudoroot
SSH type:           builtin
Dashboard URL:      http://10.x.x.211:23380/dashboard
Grafana URL:        http://10.x.x.211:3000
ID                 Role          Host         Ports        OS/Arch       Status  Data Dir                                            Deploy Dir
--                 ----          ----         -----        -------       ------  --------                                            ----------
10.x.x.211:9093   alertmanager  10.x.x.211  9093/9094    linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/alertmanager-90  /opt/tidb/tidb-7.5.1/tidb-deploy/alertmanager-90
10.x.x.211:3000   grafana       10.x.x.211  3000         linux/x86_64  Up      -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/grafana-3000
10.x.x.211:23379  pd            10.x.x.211  23379/24380  linux/x86_64  Up|L    /opt/tidb/tidb-data/tidb/tidb-data/pd-23379         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23379
10.x.x.211:23380  pd            10.x.x.211  23380/24381  linux/x86_64  Up|UI   /opt/tidb/tidb-data/tidb/tidb-data/pd-23380         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23380
10.x.x.211:23381  pd            10.x.x.211  23381/24382  linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/pd-23381         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23381
10.x.x.211:9090   prometheus    10.x.x.211  9090/12020   linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/prometheus-8249  /opt/tidb/tidb-7.5.1/tidb-deploy/prometheus-8249
10.x.x.211:4000   tidb          10.x.x.211  4000/10080   linux/x86_64  Up      -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4000
10.x.x.211:4001   tidb          10.x.x.211  4001/10081   linux/x86_64  Up      -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4001
10.x.x.211:4003   tidb          10.x.x.211  4003/10083   linux/x86_64  Up      -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4003
10.x.x.211:20160  tikv          10.x.x.211  20160/20180  linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/tikv-20160       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20160
10.x.x.211:20161  tikv          10.x.x.211  20161/20181  linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/tikv-20161       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20161
10.x.x.211:20162  tikv          10.x.x.211  20162/20182  linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/tikv-20162       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20162
Total nodes: 12
[sudoroot@ln-server-01 ~]$ tiup cluster scale-in xx-tidb --node 10.x.x.211:20162
Checking updates for component cluster... Timedout (after 2s)
This operation will delete the 10.x.x.211:20162 nodes in `xx-tidb` and all their data.
Do you want to continue? [y/N]:(default=N) y
The component `[tikv]` will become tombstone, maybe exists in several minutes or hours, after that you can use the prune command to clean it
Do you want to continue? [y/N]:(default=N) y
Scale-in nodes...
+ [ Serial ] - SSHKeySet: privateKey=/home/sudoroot/.tiup/storage/cluster/clusters/xx-tidb/ssh/id_rsa, publicKey=/home/sudoroot/.tiup/storage/cluster/clusters/xx-tidb/ssh/id_rsa.pub
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [ Serial ] - ClusterOperate: operation=DestroyOperation, options={Roles:[] Nodes:[10.x.x.211:20162] Force:false SSHTimeout:5 OptTimeout:120 APITimeout:600 IgnoreConfigCheck:false NativeSSH:false SSHType: Concurrency:5 SSHProxyHost: SSHProxyPort:22 SSHProxyUser:sudoroot SSHProxyIdentity:/home/sudoroot/.ssh/id_rsa SSHProxyUsePassword:false SSHProxyTimeout:5 SSHCustomScripts:{BeforeRestartInstance:{Raw:} AfterRestartInstance:{Raw:}} CleanupData:false CleanupLog:false CleanupAuditLog:false RetainDataRoles:[] RetainDataNodes:[] DisplayMode:default Operation:StartOperation}
The component `tikv` will become tombstone, maybe exists in several minutes or hours, after that you can use the prune command to clean it
+ [ Serial ] - UpdateMeta: cluster=xx-tidb, deleted=`''`
+ [ Serial ] - UpdateTopology: cluster=xx-tidb
+ Refresh instance configs
  - Generate config pd -> 10.x.x.211:23379 ... Done
  - Generate config pd -> 10.x.x.211:23380 ... Done
  - Generate config pd -> 10.x.x.211:23381 ... Done
  - Generate config tikv -> 10.x.x.211:20160 ... Done
  - Generate config tikv -> 10.x.x.211:20161 ... Done
  - Generate config tidb -> 10.x.x.211:4000 ... Done
  - Generate config tidb -> 10.x.x.211:4001 ... Done
  - Generate config tidb -> 10.x.x.211:4003 ... Done
  - Generate config prometheus -> 10.x.x.211:9090 ... Done
  - Generate config grafana -> 10.x.x.211:3000 ... Done
  - Generate config alertmanager -> 10.x.x.211:9093 ... Done
+ Reload prometheus and grafana
  - Reload prometheus -> 10.x.x.211:9090 ... Done
  - Reload grafana -> 10.x.x.211:3000 ... Done
Scaled cluster `xx-tidb` in successfully
[sudoroot@ln-server-01 ~]$ tiup cluster scale-in xx-tidb --node 10.x.x.211:20161
Checking updates for component cluster... Timedout (after 2s)
This operation will delete the 10.x.x.211:20161 nodes in `xx-tidb` and all their data.
Do you want to continue? [y/N]:(default=N) y
The component `[tikv]` will become tombstone, maybe exists in several minutes or hours, after that you can use the prune command to clean it
Do you want to continue? [y/N]:(default=N) y
Scale-in nodes...
+ [ Serial ] - SSHKeySet: privateKey=/home/sudoroot/.tiup/storage/cluster/clusters/xx-tidb/ssh/id_rsa, publicKey=/home/sudoroot/.tiup/storage/cluster/clusters/xx-tidb/ssh/id_rsa.pub
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [ Serial ] - ClusterOperate: operation=DestroyOperation, options={Roles:[] Nodes:[10.x.x.211:20161] Force:false SSHTimeout:5 OptTimeout:120 APITimeout:600 IgnoreConfigCheck:false NativeSSH:false SSHType: Concurrency:5 SSHProxyHost: SSHProxyPort:22 SSHProxyUser:sudoroot SSHProxyIdentity:/home/sudoroot/.ssh/id_rsa SSHProxyUsePassword:false SSHProxyTimeout:5 SSHCustomScripts:{BeforeRestartInstance:{Raw:} AfterRestartInstance:{Raw:}} CleanupData:false CleanupLog:false CleanupAuditLog:false RetainDataRoles:[] RetainDataNodes:[] DisplayMode:default Operation:StartOperation}
The component `tikv` will become tombstone, maybe exists in several minutes or hours, after that you can use the prune command to clean it
+ [ Serial ] - UpdateMeta: cluster=xx-tidb, deleted=`''`
+ [ Serial ] - UpdateTopology: cluster=xx-tidb
+ Refresh instance configs
  - Generate config pd -> 10.x.x.211:23379 ... Done
  - Generate config pd -> 10.x.x.211:23380 ... Done
  - Generate config pd -> 10.x.x.211:23381 ... Done
  - Generate config tikv -> 10.x.x.211:20160 ... Done
  - Generate config tikv -> 10.x.x.211:20162 ... Done
  - Generate config tidb -> 10.x.x.211:4000 ... Done
  - Generate config tidb -> 10.x.x.211:4001 ... Done
  - Generate config tidb -> 10.x.x.211:4003 ... Done
  - Generate config prometheus -> 10.x.x.211:9090 ... Done
  - Generate config grafana -> 10.x.x.211:3000 ... Done
  - Generate config alertmanager -> 10.x.x.211:9093 ... Done
+ Reload prometheus and grafana
  - Reload prometheus -> 10.x.x.211:9090 ... Done
  - Reload grafana -> 10.x.x.211:3000 ... Done
Scaled cluster `xx-tidb` in successfully
[sudoroot@ln-server-01 ~]$ tiup cluster display xx-tidb
Checking updates for component cluster... Timedout (after 2s)
Cluster type:       tidb
Cluster name:       xx-tidb
Cluster version:    v7.5.1
Deploy user:        sudoroot
SSH type:           builtin
Dashboard URL:      http://10.x.x.211:23380/dashboard
Grafana URL:        http://10.x.x.211:3000
ID                 Role          Host         Ports        OS/Arch       Status           Data Dir                                            Deploy Dir
--                 ----          ----         -----        -------       ------           --------                                            ----------
10.x.x.211:9093   alertmanager  10.x.x.211  9093/9094    linux/x86_64  Up               /opt/tidb/tidb-data/tidb/tidb-data/alertmanager-90  /opt/tidb/tidb-7.5.1/tidb-deploy/alertmanager-90
10.x.x.211:3000   grafana       10.x.x.211  3000         linux/x86_64  Up               -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/grafana-3000
10.x.x.211:23379  pd            10.x.x.211  23379/24380  linux/x86_64  Up|L             /opt/tidb/tidb-data/tidb/tidb-data/pd-23379         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23379
10.x.x.211:23380  pd            10.x.x.211  23380/24381  linux/x86_64  Up|UI            /opt/tidb/tidb-data/tidb/tidb-data/pd-23380         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23380
10.x.x.211:23381  pd            10.x.x.211  23381/24382  linux/x86_64  Up               /opt/tidb/tidb-data/tidb/tidb-data/pd-23381         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23381
10.x.x.211:9090   prometheus    10.x.x.211  9090/12020   linux/x86_64  Up               /opt/tidb/tidb-data/tidb/tidb-data/prometheus-8249  /opt/tidb/tidb-7.5.1/tidb-deploy/prometheus-8249
10.x.x.211:4000   tidb          10.x.x.211  4000/10080   linux/x86_64  Up               -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4000
10.x.x.211:4001   tidb          10.x.x.211  4001/10081   linux/x86_64  Up               -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4001
10.x.x.211:4003   tidb          10.x.x.211  4003/10083   linux/x86_64  Up               -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4003
10.x.x.211:20160  tikv          10.x.x.211  20160/20180  linux/x86_64  Up               /opt/tidb/tidb-data/tidb/tidb-data/tikv-20160       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20160
10.x.x.211:20161  tikv          10.x.x.211  20161/20181  linux/x86_64  Pending Offline  /opt/tidb/tidb-data/tidb/tidb-data/tikv-20161       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20161
10.x.x.211:20162  tikv          10.x.x.211  20162/20182  linux/x86_64  Pending Offline  /opt/tidb/tidb-data/tidb/tidb-data/tikv-20162       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20162
Total nodes: 12
[sudoroot@ln-server-01 ~]$

5.执行tiup cluster prune xx-tidb

复制代码 
[sudoroot@ln-server-01 ~]$ tiup cluster display xx-tidb
Checking updates for component cluster... Timedout (after 2s)
Cluster type:       tidb
Cluster name:       xx-tidb
Cluster version:    v7.5.1
Deploy user:        sudoroot
SSH type:           builtin
Dashboard URL:      http://10.x.x.211:23380/dashboard
Grafana URL:        http://10.x.x.211:3000
ID                 Role          Host         Ports        OS/Arch       Status     Data Dir                                            Deploy Dir
--                 ----          ----         -----        -------       ------     --------                                            ----------
10.x.x.211:9093   alertmanager  10.x.x.211  9093/9094    linux/x86_64  Up         /opt/tidb/tidb-data/tidb/tidb-data/alertmanager-90  /opt/tidb/tidb-7.5.1/tidb-deploy/alertmanager-90
10.x.x.211:3000   grafana       10.x.x.211  3000         linux/x86_64  Up         -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/grafana-3000
10.x.x.211:23379  pd            10.x.x.211  23379/24380  linux/x86_64  Up|L       /opt/tidb/tidb-data/tidb/tidb-data/pd-23379         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23379
10.x.x.211:23380  pd            10.x.x.211  23380/24381  linux/x86_64  Up|UI      /opt/tidb/tidb-data/tidb/tidb-data/pd-23380         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23380
10.x.x.211:23381  pd            10.x.x.211  23381/24382  linux/x86_64  Up         /opt/tidb/tidb-data/tidb/tidb-data/pd-23381         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23381
10.x.x.211:9090   prometheus    10.x.x.211  9090/12020   linux/x86_64  Up         /opt/tidb/tidb-data/tidb/tidb-data/prometheus-8249  /opt/tidb/tidb-7.5.1/tidb-deploy/prometheus-8249
10.x.x.211:4000   tidb          10.x.x.211  4000/10080   linux/x86_64  Up         -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4000
10.x.x.211:4001   tidb          10.x.x.211  4001/10081   linux/x86_64  Up         -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4001
10.x.x.211:4003   tidb          10.x.x.211  4003/10083   linux/x86_64  Up         -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4003
10.x.x.211:20160  tikv          10.x.x.211  20160/20180  linux/x86_64  Up         /opt/tidb/tidb-data/tidb/tidb-data/tikv-20160       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20160
10.x.x.211:20161  tikv          10.x.x.211  20161/20181  linux/x86_64  Tombstone  /opt/tidb/tidb-data/tidb/tidb-data/tikv-20161       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20161
10.x.x.211:20162  tikv          10.x.x.211  20162/20182  linux/x86_64  Tombstone  /opt/tidb/tidb-data/tidb/tidb-data/tikv-20162       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20162
Total nodes: 12
There are some nodes can be pruned: 
        Nodes: [10.x.x.211:20161 10.x.x.211:20162]
        You can destroy them with the command: `tiup cluster prune xx-tidb`
[sudoroot@ln-server-01 ~]$ tiup cluster prune xx-tidb
Checking updates for component cluster... Timedout (after 2s)
+ [ Serial ] - SSHKeySet: privateKey=/home/sudoroot/.tiup/storage/cluster/clusters/xx-tidb/ssh/id_rsa, publicKey=/home/sudoroot/.tiup/storage/cluster/clusters/xx-tidb/ssh/id_rsa.pub
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [Parallel] - UserSSH: user=sudoroot, host=10.x.x.211
+ [ Serial ] - FindTomestoneNodes
Will destroy these nodes: [10.x.x.211:20161 10.x.x.211:20162]
Do you confirm this action? [y/N]:(default=N) y                         
Start destroy Tombstone nodes: [10.x.x.211:20161 10.x.x.211:20162] ...
+ [ Serial ] - ClusterOperate: operation=ScaleInOperation, options={Roles:[] Nodes:[] Force:true SSHTimeout:5 OptTimeout:120 APITimeout:600 IgnoreConfigCheck:true NativeSSH:false SSHType: Concurrency:5 SSHProxyHost: SSHProxyPort:22 SSHProxyUser:sudoroot SSHProxyIdentity:/home/sudoroot/.ssh/id_rsa SSHProxyUsePassword:false SSHProxyTimeout:5 SSHCustomScripts:{BeforeRestartInstance:{Raw:} AfterRestartInstance:{Raw:}} CleanupData:false CleanupLog:false CleanupAuditLog:false RetainDataRoles:[] RetainDataNodes:[] DisplayMode:default Operation:StartOperation}
Stopping component tikv
        Stopping instance 10.x.x.211
        Stop tikv 10.x.x.211:20161 success
Destroying component tikv
        Destroying instance 10.x.x.211
Destroy 10.x.x.211 finished
- Destroy tikv paths: [/etc/systemd/system/tikv-20161.service /opt/tidb/tidb-data/tidb/tidb-data/tikv-20161 /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20161/log /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20161]
Stopping component tikv
        Stopping instance 10.x.x.211
        Stop tikv 10.x.x.211:20162 success
Destroying component tikv
        Destroying instance 10.x.x.211
Destroy 10.x.x.211 finished
- Destroy tikv paths: [/opt/tidb/tidb-data/tidb/tidb-data/tikv-20162 /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20162/log /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20162 /etc/systemd/system/tikv-20162.service]
+ [ Serial ] - UpdateMeta: cluster=xx-tidb, deleted=`'10.x.x.211:20161','10.x.x.211:20162'`
+ [ Serial ] - UpdateTopology: cluster=xx-tidb
+ Refresh instance configs
  - Generate config pd -> 10.x.x.211:23379 ... Done
  - Generate config pd -> 10.x.x.211:23380 ... Done
  - Generate config pd -> 10.x.x.211:23381 ... Done
  - Generate config tikv -> 10.x.x.211:20160 ... Done
  - Generate config tidb -> 10.x.x.211:4000 ... Done
  - Generate config tidb -> 10.x.x.211:4001 ... Done
  - Generate config tidb -> 10.x.x.211:4003 ... Done
  - Generate config prometheus -> 10.x.x.211:9090 ... Done
  - Generate config grafana -> 10.x.x.211:3000 ... Done
  - Generate config alertmanager -> 10.x.x.211:9093 ... Done
+ Reload prometheus and grafana
  - Reload prometheus -> 10.x.x.211:9090 ... Done
  - Reload grafana -> 10.x.x.211:3000 ... Done
Destroy success
[sudoroot@ln-server-01 ~]$ tiup cluster display xx-tidb
Checking updates for component cluster... Timedout (after 2s)
Cluster type:       tidb
Cluster name:       xx-tidb
Cluster version:    v7.5.1
Deploy user:        sudoroot
SSH type:           builtin
Dashboard URL:      http://10.x.x.211:23380/dashboard
Grafana URL:        http://10.x.x.211:3000
ID                 Role          Host         Ports        OS/Arch       Status  Data Dir                                            Deploy Dir
--                 ----          ----         -----        -------       ------  --------                                            ----------
10.x.x.211:9093   alertmanager  10.x.x.211  9093/9094    linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/alertmanager-90  /opt/tidb/tidb-7.5.1/tidb-deploy/alertmanager-90
10.x.x.211:3000   grafana       10.x.x.211  3000         linux/x86_64  Up      -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/grafana-3000
10.x.x.211:23379  pd            10.x.x.211  23379/24380  linux/x86_64  Up|L    /opt/tidb/tidb-data/tidb/tidb-data/pd-23379         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23379
10.x.x.211:23380  pd            10.x.x.211  23380/24381  linux/x86_64  Up|UI   /opt/tidb/tidb-data/tidb/tidb-data/pd-23380         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23380
10.x.x.211:23381  pd            10.x.x.211  23381/24382  linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/pd-23381         /opt/tidb/tidb-7.5.1/tidb-deploy/pd-23381
10.x.x.211:9090   prometheus    10.x.x.211  9090/12020   linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/prometheus-8249  /opt/tidb/tidb-7.5.1/tidb-deploy/prometheus-8249
10.x.x.211:4000   tidb          10.x.x.211  4000/10080   linux/x86_64  Up      -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4000
10.x.x.211:4001   tidb          10.x.x.211  4001/10081   linux/x86_64  Up      -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4001
10.x.x.211:4003   tidb          10.x.x.211  4003/10083   linux/x86_64  Up      -                                                   /opt/tidb/tidb-7.5.1/tidb-deploy/tidb-4003
10.x.x.211:20160  tikv          10.x.x.211  20160/20180  linux/x86_64  Up      /opt/tidb/tidb-data/tidb/tidb-data/tikv-20160       /opt/tidb/tidb-7.5.1/tidb-deploy/tikv-20160
Total nodes: 10
[sudoroot@ln-server-01 ~]$
相关推荐
高铭杰13 天前
万物皆可KV（1）TIDB存储布局分析
java·前端·tidb
TiDB 社区干货传送门14 天前
TiDB 8.5.7 发版｜六项实用功能上线
数据库·mysql·tidb
Database_Cool_24 天前
阿里云 PolarDB-X vs TiDB 分布式数据库选型指南
数据库·分布式·阿里云·tidb
睡不醒男孩0308232 个月前
TiDB数据库调研
数据库·tidb
解决问题no解决代码问题2 个月前
TiDB 深度对比：拆解三类传统扩容方案与 TiDB 原生分布式架构差异
tidb
解决问题no解决代码问题2 个月前
分区表清理操作全对比：DB2 / Oracle / MySQL / TiDB 流程详解
tidb
解决问题no解决代码问题2 个月前
TiDB 原理与节点宕机实战讲解
数据库·tidb
不爱编程的小陈2 个月前
事务的进化：从MySQL单机事务到TiDB分布式事务的探究
分布式·mysql·tidb
解决问题no解决代码问题2 个月前
深入解析 TiDB 分布式架构：三大核心组件与底层运行原理
tidb
热门推荐
01如何新建文件夹？ 电脑新建文件夹的4种方法02GitHub 镜像站点03国内可直接用、免费额度/永久免费的大模型API清单（含 SiliconFlow、火山、阿里、智谱、百度、Kimi、DeepSeek、DMXAPI 等）04AI 编程 IDE 全景解析 2026：Agent 全面接管开发链路052026 国产 AI 大模型横评：DeepSeek、通义千问、Kimi、文心一言、星火、豆包谁更能打？06Agnes AI 免费 API 接入指南：文本、生图、生视频，一套接口全免费07微信历史版本含下载地址（ Windows PC | 安卓 | MAC ）及设置微信不更新082026年7月AI圈大地震：GPT-5.6被政府限制、Claude入驻Slack、Anthropic自研芯片09历年考研数学一、数学二、数学三真题试卷及答案PDF1000 Debian字符界面如何支持中文