TiDB v7.1.0 版本 相关（部署、在线扩容、数据迁移）测试

Disable telemetry successSuccessfully set mirror to /tidb-setup/tidb-community-server-v7.1.0-linux-amd64Detected shell: bashShell profile:  /root/.bash_profileInstalled path: /root/.tiup/bin/tiup===============================================1. source /root/.bash_profile2. Have a try:   tiup playground===============================================

# # Global variables are applied to all deployments and used as the default value of# # the deployments if a specific deployment value is missing.global:  # # The user who runs the tidb cluster.  user: "tidb"  # # group is used to specify the group name the user belong to if it's not the same as user.  # group: "tidb"  # # SSH port of servers in the managed cluster.  ssh_port: 22  # # Storage directory for cluster deployment files, startup scripts, and configuration files.  deploy_dir: "/tidb-deploy"  # # TiDB Cluster data storage directory  data_dir: "/tidb-data"  # # Supported values: "amd64", "arm64" (default: "amd64")  arch: "amd64"  # # Resource Control is used to limit the resource of an instance.  # # See: https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html  # # Supports using instance-level `resource_control` to override global `resource_control`.  # resource_control:  #   # See: https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html#MemoryLimit=bytes  #   memory_limit: "2G"  #   # See: https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html#CPUQuota=  #   # The percentage specifies how much CPU time the unit shall get at maximum, relative to the total CPU time available on one CPU. Use values > 100% for allotting CPU time on more than one CPU.  #   # Example: CPUQuota=200% ensures that the executed processes will never get more than two CPU time.  #   cpu_quota: "200%"  #   # See: https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html#IOReadBandwidthMax=device%20bytes  #   io_read_bandwidth_max: "/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0 100M"  #   io_write_bandwidth_max: "/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0 100M"
# # Monitored variables are applied to all the machines.monitored:  # # The communication port for reporting system information of each node in the TiDB cluster.  node_exporter_port: 9100  # # Blackbox_exporter communication port, used for TiDB cluster port monitoring.  blackbox_exporter_port: 9115  # # Storage directory for deployment files, startup scripts, and configuration files of monitoring components.  # deploy_dir: "/tidb-deploy/monitored-9100"  # # Data storage directory of monitoring components.  # data_dir: "/tidb-data/monitored-9100"  # # Log storage directory of the monitoring component.  # log_dir: "/tidb-deploy/monitored-9100/log"
# # Server configs are used to specify the runtime configuration of TiDB components.# # All configuration items can be found in TiDB docs:# # - TiDB: https://pingcap.com/docs/stable/reference/configuration/tidb-server/configuration-file/# # - TiKV: https://pingcap.com/docs/stable/reference/configuration/tikv-server/configuration-file/# # - PD: https://pingcap.com/docs/stable/reference/configuration/pd-server/configuration-file/# # - TiFlash: https://docs.pingcap.com/tidb/stable/tiflash-configuration# ## # All configuration items use points to represent the hierarchy, e.g:# #   readpool.storage.use-unified-pool# #           ^       ^# # - example: https://github.com/pingcap/tiup/blob/master/examples/topology.example.yaml.# # You can overwrite this configuration via the instance-level `config` field.# server_configs:  # tidb:  # tikv:  # pd:  # tiflash:  # tiflash-learner:
# # Server configs are used to specify the configuration of PD Servers.pd_servers:  # # The ip address of the PD Server.  - host: 192.168.31.51    # # SSH port of the server.    # ssh_port: 22    # # PD Server name    # name: "pd-1"    # # communication port for TiDB Servers to connect.    # client_port: 2379    # # Communication port among PD Server nodes.    # peer_port: 2380    # # PD Server deployment file, startup script, configuration file storage directory.    # deploy_dir: "/tidb-deploy/pd-2379"    # # PD Server data storage directory.    # data_dir: "/tidb-data/pd-2379"    # # PD Server log file storage directory.    # log_dir: "/tidb-deploy/pd-2379/log"    # # numa node bindings.    # numa_node: "0,1"    # # The following configs are used to overwrite the `server_configs.pd` values.    # config:    #   schedule.max-merge-region-size: 20    #   schedule.max-merge-region-keys: 200000  - host: 192.168.31.52    # ssh_port: 22    # name: "pd-1"    # client_port: 2379    # peer_port: 2380    # deploy_dir: "/tidb-deploy/pd-2379"    # data_dir: "/tidb-data/pd-2379"    # log_dir: "/tidb-deploy/pd-2379/log"    # numa_node: "0,1"    # config:    #   schedule.max-merge-region-size: 20    #   schedule.max-merge-region-keys: 200000    # host: 10.0.1.13    # ssh_port: 22    # name: "pd-1"    # client_port: 2379    # peer_port: 2380    # deploy_dir: "/tidb-deploy/pd-2379"    # data_dir: "/tidb-data/pd-2379"    # log_dir: "/tidb-deploy/pd-2379/log"    # numa_node: "0,1"    # config:    #   schedule.max-merge-region-size: 20    #   schedule.max-merge-region-keys: 200000
# # Server configs are used to specify the configuration of TiDB Servers.tidb_servers:  # # The ip address of the TiDB Server.  - host: 192.168.31.50    # # SSH port of the server.    # ssh_port: 22    # # The port for clients to access the TiDB cluster.    # port: 4000    # # TiDB Server status API port.    # status_port: 10080    # # TiDB Server deployment file, startup script, configuration file storage directory.    # deploy_dir: "/tidb-deploy/tidb-4000"    # # TiDB Server log file storage directory.    # log_dir: "/tidb-deploy/tidb-4000/log"  # # The ip address of the TiDB Server.    #host: 10.0.1.15    # ssh_port: 22    # port: 4000    # status_port: 10080    # deploy_dir: "/tidb-deploy/tidb-4000"    # log_dir: "/tidb-deploy/tidb-4000/log"    #host: 10.0.1.16    # ssh_port: 22    # port: 4000    # status_port: 10080    # deploy_dir: "/tidb-deploy/tidb-4000"    # log_dir: "/tidb-deploy/tidb-4000/log"
# # Server configs are used to specify the configuration of TiKV Servers.tikv_servers:  # # The ip address of the TiKV Server.  - host: 192.168.31.53    # # SSH port of the server.    # ssh_port: 22    # # TiKV Server communication port.    # port: 20160    # # TiKV Server status API port.    # status_port: 20180    # # TiKV Server deployment file, startup script, configuration file storage directory.    # deploy_dir: "/tidb-deploy/tikv-20160"    # # TiKV Server data storage directory.    # data_dir: "/tidb-data/tikv-20160"    # # TiKV Server log file storage directory.    # log_dir: "/tidb-deploy/tikv-20160/log"    # # The following configs are used to overwrite the `server_configs.tikv` values.    # config:    #   log.level: warn  # # The ip address of the TiKV Server.  - host: 192.168.31.54    # ssh_port: 22    # port: 20160    # status_port: 20180    # deploy_dir: "/tidb-deploy/tikv-20160"    # data_dir: "/tidb-data/tikv-20160"    # log_dir: "/tidb-deploy/tikv-20160/log"    # config:    #   log.level: warn  - host: 192.168.31.55    # ssh_port: 22    # port: 20160    # status_port: 20180    # deploy_dir: "/tidb-deploy/tikv-20160"    # data_dir: "/tidb-data/tikv-20160"    # log_dir: "/tidb-deploy/tikv-20160/log"    # config:    #   log.level: warn
# # Server configs are used to specify the configuration of TiFlash Servers.tiflash_servers:  # # The ip address of the TiFlash Server.  - host: 192.168.31.57    # # SSH port of the server.    # ssh_port: 22    # # TiFlash TCP Service port.    # tcp_port: 9000    # # TiFlash raft service and coprocessor service listening address.    # flash_service_port: 3930    # # TiFlash Proxy service port.    # flash_proxy_port: 20170    # # TiFlash Proxy metrics port.    # flash_proxy_status_port: 20292    # # TiFlash metrics port.    # metrics_port: 8234    # # TiFlash Server deployment file, startup script, configuration file storage directory.    # deploy_dir: /tidb-deploy/tiflash-9000    ## With cluster version >= v4.0.9 and you want to deploy a multi-disk TiFlash node, it is recommended to    ## check config.storage.* for details. The data_dir will be ignored if you defined those configurations.    ## Setting data_dir to a ','-joined string is still supported but deprecated.    ## Check https://docs.pingcap.com/tidb/stable/tiflash-configuration#multi-disk-deployment for more details.    # # TiFlash Server data storage directory.    # data_dir: /tidb-data/tiflash-9000    # # TiFlash Server log file storage directory.    # log_dir: /tidb-deploy/tiflash-9000/log  # # The ip address of the TiKV Server.    #host: 10.0.1.21    # ssh_port: 22    # tcp_port: 9000    # flash_service_port: 3930    # flash_proxy_port: 20170    # flash_proxy_status_port: 20292    # metrics_port: 8234    # deploy_dir: /tidb-deploy/tiflash-9000    # data_dir: /tidb-data/tiflash-9000    # log_dir: /tidb-deploy/tiflash-9000/log
# # Server configs are used to specify the configuration of Prometheus Server.  monitoring_servers:  # # The ip address of the Monitoring Server.  - host: 192.168.31.57    # # SSH port of the server.    # ssh_port: 22    # # Prometheus Service communication port.    # port: 9090    # # ng-monitoring servive communication port    # ng_port: 12020    # # Prometheus deployment file, startup script, configuration file storage directory.    # deploy_dir: "/tidb-deploy/prometheus-8249"    # # Prometheus data storage directory.    # data_dir: "/tidb-data/prometheus-8249"    # # Prometheus log file storage directory.    # log_dir: "/tidb-deploy/prometheus-8249/log"
# # Server configs are used to specify the configuration of Grafana Servers.  grafana_servers:  # # The ip address of the Grafana Server.  - host: 192.168.31.57    # # Grafana web port (browser access)    # port: 3000    # # Grafana deployment file, startup script, configuration file storage directory.    # deploy_dir: /tidb-deploy/grafana-3000
# # Server configs are used to specify the configuration of Alertmanager Servers.  alertmanager_servers:  # # The ip address of the Alertmanager Server.  - host: 192.168.31.57    # # SSH port of the server.    # ssh_port: 22    # # Alertmanager web service port.    # web_port: 9093    # # Alertmanager communication port.    # cluster_port: 9094    # # Alertmanager deployment file, startup script, configuration file storage directory.    # deploy_dir: "/tidb-deploy/alertmanager-9093"    # # Alertmanager data storage directory.    # data_dir: "/tidb-data/alertmanager-9093"    # # Alertmanager log file storage directory.    # log_dir: "/tidb-deploy/alertmanager-9093/log"

Node           Check         Result  Message----           -----         ------  -------192.168.31.54  disk          Warn    mount point / does not have 'noatime' option set192.168.31.54  cpu-governor  Warn    Unable to determine current CPU frequency governor policy192.168.31.54  service       Fail    service firewalld is running but should be stopped192.168.31.54  swap          Warn    swap is enabled, please disable it for best performance192.168.31.54  thp           Fail    THP is enabled, please disable it for best performance192.168.31.55  swap          Warn    swap is enabled, please disable it for best performance192.168.31.55  disk          Warn    mount point / does not have 'noatime' option set192.168.31.55  service       Fail    service firewalld is running but should be stopped192.168.31.55  cpu-governor  Warn    Unable to determine current CPU frequency governor policy192.168.31.55  thp           Fail    THP is enabled, please disable it for best performance192.168.31.50  service       Fail    service firewalld is running but should be stopped192.168.31.50  cpu-governor  Warn    Unable to determine current CPU frequency governor policy192.168.31.50  swap          Warn    swap is enabled, please disable it for best performance192.168.31.50  thp           Fail    THP is enabled, please disable it for best performance192.168.31.57  command       Fail    numactl not usable, bash: numactl: command not found192.168.31.57  disk          Warn    mount point / does not have 'noatime' option set192.168.31.57  sysctl        Fail    net.core.somaxconn = 128, should be greater than 32768192.168.31.57  sysctl        Fail    net.ipv4.tcp_syncookies = 1, should be 0192.168.31.57  sysctl        Fail    vm.swappiness = 30, should be 0192.168.31.57  thp           Fail    THP is enabled, please disable it for best performance192.168.31.57  cpu-governor  Warn    Unable to determine current CPU frequency governor policy192.168.31.57  swap          Warn    swap is enabled, please disable it for best performance192.168.31.57  selinux       Fail    SELinux is not disabled192.168.31.57  service       Fail    service firewalld is running but should be stopped192.168.31.57  limits        Fail    soft limit of 'nofile' for user 'tidb' is not set or too low192.168.31.57  limits        Fail    hard limit of 'nofile' for user 'tidb' is not set or too low192.168.31.57  limits        Fail    soft limit of 'stack' for user 'tidb' is not set or too low192.168.31.51  cpu-governor  Warn    Unable to determine current CPU frequency governor policy192.168.31.51  disk          Warn    mount point / does not have 'noatime' option set192.168.31.51  service       Fail    service firewalld is running but should be stopped 192.168.31.51  swap          Warn    swap is enabled, please disable it for best performance192.168.31.51  thp           Fail    THP is enabled, please disable it for best performance192.168.31.52  service       Fail    service firewalld is running but should be stopped192.168.31.52  cpu-governor  Warn    Unable to determine current CPU frequency governor policyB192.168.31.52  disk          Warn    mount point / does not have 'noatime' option set192.168.31.52  swap          Warn    swap is enabled, please disable it for best performance192.168.31.52  thp           Fail    THP is enabled, please disable it for best performance192.168.31.53  disk          Warn    mount point / does not have 'noatime' option set192.168.31.53  thp           Fail    THP is enabled, please disable it for best performance192.168.31.53  service       Fail    service firewalld is running but should be stopped192.168.31.53  cpu-governor  Warn    Unable to determine current CPU frequency governor policy192.168.31.53  swap          Warn    swap is enabled, please disable it for best performance

[root@192_168_31_50_TiDB tidb-community-server-v7.1.0-linux-amd64]# tiup cluster check ./tidb_install.yaml --apply --user root -p 

[root@192_168_31_57_Dashboard ~]# yum -y install numactlFailed to set locale, defaulting to CLoaded plugins: fastestmirrorDetermining fastest mirrors * base: mirrors.aliyun.com * extras: mirrors.aliyun.com * updates: mirrors.aliyun.combase                                                     | 3.6 kB     00:00     extras                                                   | 2.9 kB     00:00     updates                                                  | 2.9 kB     00:00     (1/4): extras/7/x86_64/primary_db                          | 249 kB   00:00     (2/4): base/7/x86_64/group_gz                              | 153 kB   00:00     (3/4): base/7/x86_64/primary_db                            | 6.1 MB   00:00     (4/4): updates/7/x86_64/primary_db                         |  21 MB   00:01     Resolving Dependencies--> Running transaction check---> Package numactl.x86_64 0:2.0.12-5.el7 will be installed--> Finished Dependency Resolution
Dependencies Resolved
================================================================================ Package           Arch             Version                Repository      Size================================================================================Installing: numactl           x86_64           2.0.12-5.el7           base            66 k
Transaction Summary================================================================================Install  1 Package
Total download size: 66 kInstalled size: 141 kDownloading packages:warning: /var/cache/yum/x86_64/7/base/packages/numactl-2.0.12-5.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEYPublic key for numactl-2.0.12-5.el7.x86_64.rpm is not installed

[root@192_168_31_50_TiDB tidb-community-server-v7.1.0-linux-amd64]# tiup cluster check ./tidb_install.yaml --user root -p Input SSH password: 

[root@192_168_31_50_TiDB tidb-community-server-v7.1.0-linux-amd64]# tiup cluster deploy tidb-lab v7.1.0 ./tidb_install.yaml --user root -p tiup is checking updates for component cluster ...Starting component `cluster`: /root/.tiup/components/cluster/v1.12.2/tiup-cluster deploy tidb-lab v7.1.0 ./tidb_install.yaml --user root -pInput SSH password: 

+ Detect CPU Arch Name  - Detecting node 192.168.31.51 Arch info ... ⠹ Shell: host=192.168.31.51, sudo=false, command=`uname -m`+ Detect CPU Arch Name  - Detecting node 192.168.31.51 Arch info ... Done  - Detecting node 192.168.31.52 Arch info ... Done  - Detecting node 192.168.31.53 Arch info ... Done  - Detecting node 192.168.31.54 Arch info ... Done  - Detecting node 192.168.31.55 Arch info ... Done  - Detecting node 192.168.31.50 Arch info ... Done  - Detecting node 192.168.31.57 Arch info ... Done


+ Detect CPU OS Name  - Detecting node 192.168.31.51 OS info ... ⠹ Shell: host=192.168.31.51, sudo=false, command=`uname -s`+ Detect CPU OS Name  - Detecting node 192.168.31.51 OS info ... Done  - Detecting node 192.168.31.52 OS info ... Done  - Detecting node 192.168.31.53 OS info ... Done  - Detecting node 192.168.31.54 OS info ... Done  - Detecting node 192.168.31.55 OS info ... Done  - Detecting node 192.168.31.50 OS info ... Done  - Detecting node 192.168.31.57 OS info ... DonePlease confirm your topology:Cluster type:    tidbCluster name:    tidb-labCluster version: v7.1.0Role          Host           Ports                            OS/Arch       Directories----          ----           -----                            -------       -----------pd            192.168.31.51  2379/2380                        linux/x86_64  /tidb-deploy/pd-2379,/tidb-data/pd-2379pd            192.168.31.52  2379/2380                        linux/x86_64  /tidb-deploy/pd-2379,/tidb-data/pd-2379tikv          192.168.31.53  20160/20180                      linux/x86_64  /tidb-deploy/tikv-20160,/tidb-data/tikv-20160tikv          192.168.31.54  20160/20180                      linux/x86_64  /tidb-deploy/tikv-20160,/tidb-data/tikv-20160tikv          192.168.31.55  20160/20180                      linux/x86_64  /tidb-deploy/tikv-20160,/tidb-data/tikv-20160tidb          192.168.31.50  4000/10080                       linux/x86_64  /tidb-deploy/tidb-4000tiflash       192.168.31.57  9000/8123/3930/20170/20292/8234  linux/x86_64  /tidb-deploy/tiflash-9000,/tidb-data/tiflash-9000prometheus    192.168.31.57  9090/12020                       linux/x86_64  /tidb-deploy/prometheus-9090,/tidb-data/prometheus-9090grafana       192.168.31.57  3000                             linux/x86_64  /tidb-deploy/grafana-3000alertmanager  192.168.31.57  9093/9094                        linux/x86_64  /tidb-deploy/alertmanager-9093,/tidb-data/alertmanager-9093Attention:    1. If the topology is not what you expected, check your yaml file.    2. Please confirm there is no port/directory conflicts in same host.Do you want to continue? [y/N]: (default=N) y+ Generate SSH keys ... Done+ Download TiDB components  - Download pd:v7.1.0 (linux/amd64) ... Done  - Download tikv:v7.1.0 (linux/amd64) ... Done  - Download tidb:v7.1.0 (linux/amd64) ... Done  - Download tiflash:v7.1.0 (linux/amd64) ... Done  - Download prometheus:v7.1.0 (linux/amd64) ... Done  - Download grafana:v7.1.0 (linux/amd64) ... Done  - Download alertmanager: (linux/amd64) ... Done  - Download node_exporter: (linux/amd64) ... Done  - Download blackbox_exporter: (linux/amd64) ... Done+ Initialize target host environments  - Prepare 192.168.31.54:22 ... Done  - Prepare 192.168.31.55:22 ... Done  - Prepare 192.168.31.50:22 ... Done  - Prepare 192.168.31.57:22 ... Done  - Prepare 192.168.31.51:22 ... Done  - Prepare 192.168.31.52:22 ... Done  - Prepare 192.168.31.53:22 ... Done+ Deploy TiDB instance  - Copy pd -> 192.168.31.51 ... Done  - Copy pd -> 192.168.31.52 ... Done  - Copy tikv -> 192.168.31.53 ... Done  - Copy tikv -> 192.168.31.54 ... Done  - Copy tikv -> 192.168.31.55 ... Done  - Copy tidb -> 192.168.31.50 ... Done  - Copy tiflash -> 192.168.31.57 ... Done  - Copy prometheus -> 192.168.31.57 ... Done  - Copy grafana -> 192.168.31.57 ... Done  - Copy alertmanager -> 192.168.31.57 ... Done  - Deploy node_exporter -> 192.168.31.51 ... Done  - Deploy node_exporter -> 192.168.31.52 ... Done  - Deploy node_exporter -> 192.168.31.53 ... Done  - Deploy node_exporter -> 192.168.31.54 ... Done  - Deploy node_exporter -> 192.168.31.55 ... Done  - Deploy node_exporter -> 192.168.31.50 ... Done  - Deploy node_exporter -> 192.168.31.57 ... Done  - Deploy blackbox_exporter -> 192.168.31.53 ... Done  - Deploy blackbox_exporter -> 192.168.31.54 ... Done  - Deploy blackbox_exporter -> 192.168.31.55 ... Done  - Deploy blackbox_exporter -> 192.168.31.50 ... Done  - Deploy blackbox_exporter -> 192.168.31.57 ... Done  - Deploy blackbox_exporter -> 192.168.31.51 ... Done  - Deploy blackbox_exporter -> 192.168.31.52 ... Done+ Copy certificate to remote host+ Init instance configs  - Generate config pd -> 192.168.31.51:2379 ... Done  - Generate config pd -> 192.168.31.52:2379 ... Done  - Generate config tikv -> 192.168.31.53:20160 ... Done  - Generate config tikv -> 192.168.31.54:20160 ... Done  - Generate config tikv -> 192.168.31.55:20160 ... Done  - Generate config tidb -> 192.168.31.50:4000 ... Done  - Generate config tiflash -> 192.168.31.57:9000 ... Done  - Generate config prometheus -> 192.168.31.57:9090 ... Done  - Generate config grafana -> 192.168.31.57:3000 ... Done  - Generate config alertmanager -> 192.168.31.57:9093 ... Done+ Init monitor configs  - Generate config node_exporter -> 192.168.31.55 ... Done  - Generate config node_exporter -> 192.168.31.50 ... Done  - Generate config node_exporter -> 192.168.31.57 ... Done  - Generate config node_exporter -> 192.168.31.51 ... Done  - Generate config node_exporter -> 192.168.31.52 ... Done  - Generate config node_exporter -> 192.168.31.53 ... Done  - Generate config node_exporter -> 192.168.31.54 ... Done  - Generate config blackbox_exporter -> 192.168.31.57 ... Done  - Generate config blackbox_exporter -> 192.168.31.51 ... Done  - Generate config blackbox_exporter -> 192.168.31.52 ... Done  - Generate config blackbox_exporter -> 192.168.31.53 ... Done  - Generate config blackbox_exporter -> 192.168.31.54 ... Done  - Generate config blackbox_exporter -> 192.168.31.55 ... Done  - Generate config blackbox_exporter -> 192.168.31.50 ... DoneEnabling component pd    Enabling instance 192.168.31.52:2379    Enabling instance 192.168.31.51:2379    Enable instance 192.168.31.52:2379 success    Enable instance 192.168.31.51:2379 successEnabling component tikv    Enabling instance 192.168.31.55:20160    Enabling instance 192.168.31.53:20160    Enabling instance 192.168.31.54:20160    Enable instance 192.168.31.53:20160 success    Enable instance 192.168.31.55:20160 success    Enable instance 192.168.31.54:20160 successEnabling component tidb    Enabling instance 192.168.31.50:4000    Enable instance 192.168.31.50:4000 successEnabling component tiflash    Enabling instance 192.168.31.57:9000    Enable instance 192.168.31.57:9000 successEnabling component prometheus    Enabling instance 192.168.31.57:9090    Enable instance 192.168.31.57:9090 successEnabling component grafana    Enabling instance 192.168.31.57:3000    Enable instance 192.168.31.57:3000 successEnabling component alertmanager    Enabling instance 192.168.31.57:9093    Enable instance 192.168.31.57:9093 successEnabling component node_exporter    Enabling instance 192.168.31.51    Enabling instance 192.168.31.52    Enabling instance 192.168.31.54    Enabling instance 192.168.31.50    Enabling instance 192.168.31.55    Enabling instance 192.168.31.57    Enabling instance 192.168.31.53    Enable 192.168.31.51 success    Enable 192.168.31.53 success    Enable 192.168.31.52 success    Enable 192.168.31.55 success    Enable 192.168.31.54 success    Enable 192.168.31.50 success    Enable 192.168.31.57 successEnabling component blackbox_exporter    Enabling instance 192.168.31.51    Enabling instance 192.168.31.54    Enabling instance 192.168.31.55    Enabling instance 192.168.31.50    Enabling instance 192.168.31.57    Enabling instance 192.168.31.53    Enabling instance 192.168.31.52    Enable 192.168.31.51 success    Enable 192.168.31.54 success    Enable 192.168.31.55 success    Enable 192.168.31.53 success    Enable 192.168.31.52 success    Enable 192.168.31.50 success    Enable 192.168.31.57 successCluster `tidb-lab` deployed successfully, you can start it with command: `tiup cluster start tidb-lab --init

[root@192_168_31_50_TiDB tidb-community-server-v7.1.0-linux-amd64]# tiup cluster start tidb-lab --inittiup is checking updates for component cluster ...Starting component `cluster`: /root/.tiup/components/cluster/v1.12.2/tiup-cluster start tidb-lab --initStarting cluster tidb-lab...+ [ Serial ] - SSHKeySet: privateKey=/root/.tiup/storage/cluster/clusters/tidb-lab/ssh/id_rsa, publicKey=/root/.tiup/storage/cluster/clusters/tidb-lab/ssh/id_rsa.pub+ [Parallel] - UserSSH: user=tidb, host=192.168.31.55+ [Parallel] - UserSSH: user=tidb, host=192.168.31.53+ [Parallel] - UserSSH: user=tidb, host=192.168.31.52+ [Parallel] - UserSSH: user=tidb, host=192.168.31.51+ [Parallel] - UserSSH: user=tidb, host=192.168.31.50+ [Parallel] - UserSSH: user=tidb, host=192.168.31.57+ [Parallel] - UserSSH: user=tidb, host=192.168.31.57+ [Parallel] - UserSSH: user=tidb, host=192.168.31.57+ [Parallel] - UserSSH: user=tidb, host=192.168.31.57+ [Parallel] - UserSSH: user=tidb, host=192.168.31.54+ [ Serial ] - StartClusterStarting component pd    Starting instance 192.168.31.52:2379    Starting instance 192.168.31.51:2379    Start instance 192.168.31.51:2379 success    Start instance 192.168.31.52:2379 successStarting component tikv    Starting instance 192.168.31.55:20160    Starting instance 192.168.31.53:20160    Starting instance 192.168.31.54:20160    Start instance 192.168.31.53:20160 success    Start instance 192.168.31.55:20160 success    Start instance 192.168.31.54:20160 successStarting component tidb    Starting instance 192.168.31.50:4000    Start instance 192.168.31.50:4000 successStarting component tiflash    Starting instance 192.168.31.57:9000    Start instance 192.168.31.57:9000 successStarting component prometheus    Starting instance 192.168.31.57:9090    Start instance 192.168.31.57:9090 successStarting component grafana    Starting instance 192.168.31.57:3000    Start instance 192.168.31.57:3000 successStarting component alertmanager    Starting instance 192.168.31.57:9093    Start instance 192.168.31.57:9093 successStarting component node_exporter    Starting instance 192.168.31.52    Starting instance 192.168.31.55    Starting instance 192.168.31.57    Starting instance 192.168.31.51    Starting instance 192.168.31.50    Starting instance 192.168.31.54    Starting instance 192.168.31.53    Start 192.168.31.52 success    Start 192.168.31.54 success    Start 192.168.31.55 success    Start 192.168.31.53 success    Start 192.168.31.50 success    Start 192.168.31.51 success    Start 192.168.31.57 successStarting component blackbox_exporter    Starting instance 192.168.31.52    Starting instance 192.168.31.55    Starting instance 192.168.31.50    Starting instance 192.168.31.51    Starting instance 192.168.31.54    Starting instance 192.168.31.53    Starting instance 192.168.31.57    Start 192.168.31.52 success    Start 192.168.31.55 success    Start 192.168.31.53 success    Start 192.168.31.54 success    Start 192.168.31.51 success    Start 192.168.31.50 success    Start 192.168.31.57 success+ [ Serial ] - UpdateTopology: cluster=tidb-labStarted cluster `tidb-lab` successfullyThe root password of TiDB database has been changed.The new password is: 'g@7Qa^2tbxU_w3510+'.Copy and record it to somewhere safe, it is only displayed once, and will not be stored.The generated password can NOT be get and shown again.

tom@Toms-MBP ~ % mysql -h 192.168.31.50 -P 4000 -u root -pg@7Qa^2tbxU_w3510+

mysql: [Warning] Using a password on the command line interface can be insecure.Welcome to the MySQL monitor.  Commands end with ; or \g.Your MySQL connection id is 409Server version: 5.7.25-TiDB-v7.1.0 TiDB Server (Apache License 2.0) Community Edition, MySQL 5.7 compatible
Copyright (c) 2000, 2023, Oracle and/or its affiliates.
Oracle is a registered trademark of Oracle Corporation and/or itsaffiliates. Other names may be trademarks of their respectiveowners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> set password = password ('P@ssw0rd');Query OK, 0 rows affected (0.11 sec)
mysql> 

tom@Toms-MBP ~ % mysql -h 192.168.31.50 -P 4000 -u root -pP@ssw0rd 

tom@Toms-MBP ~ % mysql -h 192.168.31.50 -P 4000 -u root -pP@ssw0rd mysql: [Warning] Using a password on the command line interface can be insecure.Welcome to the MySQL monitor.  Commands end with ; or \g.Your MySQL connection id is 411Server version: 5.7.25-TiDB-v7.1.0 TiDB Server (Apache License 2.0) Community Edition, MySQL 5.7 compatible
Copyright (c) 2000, 2023, Oracle and/or its affiliates.
Oracle is a registered trademark of Oracle Corporation and/or itsaffiliates. Other names may be trademarks of their respectiveowners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> show databases;+--------------------+| Database           |+--------------------+| INFORMATION_SCHEMA || METRICS_SCHEMA     || PERFORMANCE_SCHEMA || mysql              || test               |+--------------------+5 rows in set (0.01 sec)

[root@192_168_31_50_TiDB tidb-community-server-v7.1.0-linux-amd64]# tiup cluster display tidb-labtiup is checking updates for component cluster ...Starting component `cluster`: /root/.tiup/components/cluster/v1.12.2/tiup-cluster display tidb-labCluster type:       tidbCluster name:       tidb-labCluster version:    v7.1.0Deploy user:        tidbSSH type:           builtinDashboard URL:      http://192.168.31.51:2379/dashboardGrafana URL:        http://192.168.31.57:3000ID                   Role          Host           Ports                            OS/Arch       Status   Data Dir                      Deploy Dir--                   ----          ----           -----                            -------       ------   --------                      ----------192.168.31.57:9093   alertmanager  192.168.31.57  9093/9094                        linux/x86_64  Up       /tidb-data/alertmanager-9093  /tidb-deploy/alertmanager-9093192.168.31.57:3000   grafana       192.168.31.57  3000                             linux/x86_64  Up       -                             /tidb-deploy/grafana-3000192.168.31.51:2379   pd            192.168.31.51  2379/2380                        linux/x86_64  Up|L|UI  /tidb-data/pd-2379            /tidb-deploy/pd-2379192.168.31.52:2379   pd            192.168.31.52  2379/2380                        linux/x86_64  Up       /tidb-data/pd-2379            /tidb-deploy/pd-2379192.168.31.57:9090   prometheus    192.168.31.57  9090/12020                       linux/x86_64  Up       /tidb-data/prometheus-9090    /tidb-deploy/prometheus-9090192.168.31.50:4000   tidb          192.168.31.50  4000/10080                       linux/x86_64  Up       -                             /tidb-deploy/tidb-4000192.168.31.57:9000   tiflash       192.168.31.57  9000/8123/3930/20170/20292/8234  linux/x86_64  Up       /tidb-data/tiflash-9000       /tidb-deploy/tiflash-9000192.168.31.53:20160  tikv          192.168.31.53  20160/20180                      linux/x86_64  Up       /tidb-data/tikv-20160         /tidb-deploy/tikv-20160192.168.31.54:20160  tikv          192.168.31.54  20160/20180                      linux/x86_64  Up       /tidb-data/tikv-20160         /tidb-deploy/tikv-20160192.168.31.55:20160  tikv          192.168.31.55  20160/20180                      linux/x86_64  Up       /tidb-data/tikv-20160         /tidb-deploy/tikv-20160

tom@Toms-MBP ~ % mysql -h 192.168.31.50 -P 4000 -u root -pP@ssw0rdmysql: [Warning] Using a password on the command line interface can be insecure.Welcome to the MySQL monitor.  Commands end with ; or \g.Your MySQL connection id is 521Server version: 5.7.25-TiDB-v7.1.0 TiDB Server (Apache License 2.0) Community Edition, MySQL 5.7 compatible
Copyright (c) 2000, 2023, Oracle and/or its affiliates.
Oracle is a registered trademark of Oracle Corporation and/or itsaffiliates. Other names may be trademarks of their respectiveowners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> select * from mysql.tidb;+--------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------+| VARIABLE_NAME            | VARIABLE_VALUE                                                                                      | COMMENT                                                                                     |+--------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------+| bootstrapped             | True                                                                                                | Bootstrap flag. Do not delete.                                                              || tidb_server_version      | 146                                                                                                 | Bootstrap version. Do not delete.                                                           || system_tz                | Asia/Shanghai                                                                                       | TiDB Global System Timezone.                                                                || new_collation_enabled    | True                                                                                                | If the new collations are enabled. Do not edit it.                                          || tikv_gc_leader_uuid      | 622259489f40009                                                                                     | Current GC worker leader UUID. (DO NOT EDIT)                                                || tikv_gc_leader_desc      | host:192_168_31_50_TiDB, pid:8607, start at 2023-06-05 10:31:26.645091475 +0800 CST m=+41.567402185 | Host name and pid of current GC leader. (DO NOT EDIT)                                       || tikv_gc_leader_lease     | 20230605-11:05:26.931 +0800                                                                         | Current GC worker leader lease. (DO NOT EDIT)                                               || tikv_gc_auto_concurrency | true                                                                                                | Let TiDB pick the concurrency automatically. If set false, tikv_gc_concurrency will be used || tikv_gc_enable           | true                                                                                                | Current GC enable status                                                                    || tikv_gc_run_interval     | 10m0s                                                                                               | GC run interval, at least 10m, in Go format.                                                || tikv_gc_life_time        | 10m0s                                                                                               | All versions within life time will not be collected by GC, at least 10m, in Go format.      || tikv_gc_last_run_time    | 20230605-11:02:26.989 +0800                                                                         | The time when last GC starts. (DO NOT EDIT)                                                 || tikv_gc_safe_point       | 20230605-10:52:26.989 +0800                                                                         | All versions after safe point can be accessed. (DO NOT EDIT)                                || tikv_gc_scan_lock_mode   | legacy                                                                                              | Mode of scanning locks, "physical" or "legacy"                                              || tikv_gc_mode             | distributed                                                                                         | Mode of GC, "central" or "distributed"                                                      |+--------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------+15 rows in set (0.00 sec)

[root@192_168_31_50_TiDB tidb-community-server-v7.1.0-linux-amd64]# vim scale-out.yml

tikv_servers:  - host: 192.168.31.56    ssh_port: 22    port: 20160    status_port: 20180    deploy_dir: /tidb-deploy/tikv-20160    data_dir: /tidb-data/tikv-20160    log_dir: /tidb-deploy/tikv-20160/log

[root@192_168_31_50_TiDB tidb-community-server-v7.1.0-linux-amd64]# tiup cluster edit-config tidb-lab

global:  user: tidb  ssh_port: 22  ssh_type: builtin  deploy_dir: /tidb-deploy  data_dir: /tidb-data  os: linux  arch: amd64monitored:  node_exporter_port: 9100  blackbox_exporter_port: 9115  deploy_dir: /tidb-deploy/monitor-9100  data_dir: /tidb-data/monitor-9100  log_dir: /tidb-deploy/monitor-9100/logtidb_servers:- host: 192.168.31.50  ssh_port: 22  port: 4000  status_port: 10080  deploy_dir: /tidb-deploy/tidb-4000  log_dir: /tidb-deploy/tidb-4000/log  arch: amd64  os: linuxtikv_servers:- host: 192.168.31.53  ssh_port: 22  port: 20160  status_port: 20180  deploy_dir: /tidb-deploy/tikv-20160  data_dir: /tidb-data/tikv-20160  log_dir: /tidb-deploy/tikv-20160/log  arch: amd64  os: linux- host: 192.168.31.54  ssh_port: 22  port: 20160  status_port: 20180  deploy_dir: /tidb-deploy/tikv-20160  data_dir: /tidb-data/tikv-20160  log_dir: /tidb-deploy/tikv-20160/log  arch: amd64  os: linux- host: 192.168.31.55  ssh_port: 22  port: 20160  status_port: 20180  deploy_dir: /tidb-deploy/tikv-20160  data_dir: /tidb-data/tikv-20160  log_dir: /tidb-deploy/tikv-20160/log  arch: amd64  os: linuxtiflash_servers:- host: 192.168.31.57  ssh_port: 22  tcp_port: 9000  http_port: 8123  flash_service_port: 3930  flash_proxy_port: 20170  flash_proxy_status_port: 20292  metrics_port: 8234  deploy_dir: /tidb-deploy/tiflash-9000  data_dir: /tidb-data/tiflash-9000  log_dir: /tidb-deploy/tiflash-9000/log  arch: amd64  os: linuxpd_servers:- host: 192.168.31.51  ssh_port: 22  name: pd-192.168.31.51-2379  client_port: 2379  peer_port: 2380  deploy_dir: /tidb-deploy/pd-2379  data_dir: /tidb-data/pd-2379  log_dir: /tidb-deploy/pd-2379/log  arch: amd64  os: linux- host: 192.168.31.52  ssh_port: 22  name: pd-192.168.31.52-2379  client_port: 2379  peer_port: 2380  deploy_dir: /tidb-deploy/pd-2379  data_dir: /tidb-data/pd-2379  log_dir: /tidb-deploy/pd-2379/log  arch: amd64  os: linuxmonitoring_servers:- host: 192.168.31.57  ssh_port: 22  port: 9090  ng_port: 12020  deploy_dir: /tidb-deploy/prometheus-9090  data_dir: /tidb-data/prometheus-9090  log_dir: /tidb-deploy/prometheus-9090/log  external_alertmanagers: []  arch: amd64  os: linuxgrafana_servers:- host: 192.168.31.57  ssh_port: 22  port: 3000  deploy_dir: /tidb-deploy/grafana-3000  arch: amd64  os: linux  username: admin  password: admin  anonymous_enable: false  root_url: ""  domain: ""alertmanager_servers:- host: 192.168.31.57  ssh_port: 22  web_port: 9093  cluster_port: 9094  deploy_dir: /tidb-deploy/alertmanager-9093  data_dir: /tidb-data/alertmanager-9093  log_dir: /tidb-deploy/alertmanager-9093/log  arch: amd64  os: linux

[root@192_168_31_50_TiDB tidb-community-server-v7.1.0-linux-amd64]# tiup cluster check tidb-lab scale-out.yml --cluster --user root -p

[root@192_168_31_50_TiDB tidb-community-server-v7.1.0-linux-amd64]# tiup cluster check tidb-lab scale-out.yml --cluster --apply --user root -p

[root@192_168_31_50_TiDB tidb-community-server-v7.1.0-linux-amd64]# tiup cluster scale-out tidb-lab scale-out.yml -p

[root@192_168_31_50_TiDB tidb-community-server-v7.1.0-linux-amd64]# tiup cluster scale-out tidb-lab scale-out.yml -ptiup is checking updates for component cluster ...Starting component `cluster`: /root/.tiup/components/cluster/v1.12.2/tiup-cluster scale-out tidb-lab scale-out.yml -pInput SSH password: 
+ Detect CPU Arch Name  - Detecting node 192.168.31.56 Arch info ... Done
+ Detect CPU OS Name  - Detecting node 192.168.31.56 OS info ... DonePlease confirm your topology:Cluster type:    tidbCluster name:    tidb-labCluster version: v7.1.0Role  Host           Ports        OS/Arch       Directories----  ----           -----        -------       -----------tikv  192.168.31.56  20160/20180  linux/x86_64  /tidb-deploy/tikv-20160,/tidb-data/tikv-20160Attention:    1. If the topology is not what you expected, check your yaml file.    2. Please confirm there is no port/directory conflicts in same host.Do you want to continue? [y/N]: (default=N) y+ [ Serial ] - SSHKeySet: privateKey=/root/.tiup/storage/cluster/clusters/tidb-lab/ssh/id_rsa, publicKey=/root/.tiup/storage/cluster/clusters/tidb-lab/ssh/id_rsa.pub+ [Parallel] - UserSSH: user=tidb, host=192.168.31.55+ [Parallel] - UserSSH: user=tidb, host=192.168.31.52+ [Parallel] - UserSSH: user=tidb, host=192.168.31.50+ [Parallel] - UserSSH: user=tidb, host=192.168.31.57+ [Parallel] - UserSSH: user=tidb, host=192.168.31.53+ [Parallel] - UserSSH: user=tidb, host=192.168.31.57+ [Parallel] - UserSSH: user=tidb, host=192.168.31.54+ [Parallel] - UserSSH: user=tidb, host=192.168.31.57+ [Parallel] - UserSSH: user=tidb, host=192.168.31.57+ [Parallel] - UserSSH: user=tidb, host=192.168.31.51+ Download TiDB components  - Download tikv:v7.1.0 (linux/amd64) ... Done  - Download node_exporter: (linux/amd64) ... Done  - Download blackbox_exporter: (linux/amd64) ... Done+ Initialize target host environments  - Initialized host 192.168.31.56  ... Done+ Deploy TiDB instance  - Deploy instance tikv -> 192.168.31.56:20160 ... Done  - Deploy node_exporter -> 192.168.31.56 ... Done  - Deploy blackbox_exporter -> 192.168.31.56 ... Done+ Copy certificate to remote host+ Generate scale-out config  - Generate scale-out config tikv -> 192.168.31.56:20160 ... Done+ Init monitor config  - Generate config node_exporter -> 192.168.31.56 ... Done  - Generate config blackbox_exporter -> 192.168.31.56 ... DoneEnabling component tikv    Enabling instance 192.168.31.56:20160    Enable instance 192.168.31.56:20160 successEnabling component node_exporter    Enabling instance 192.168.31.56    Enable 192.168.31.56 successEnabling component blackbox_exporter    Enabling instance 192.168.31.56    Enable 192.168.31.56 success+ [ Serial ] - Save meta+ [ Serial ] - Start new instancesStarting component tikv    Starting instance 192.168.31.56:20160    Start instance 192.168.31.56:20160 successStarting component node_exporter    Starting instance 192.168.31.56    Start 192.168.31.56 successStarting component blackbox_exporter    Starting instance 192.168.31.56    Start 192.168.31.56 success+ Refresh components conifgs  - Generate config pd -> 192.168.31.51:2379 ... Done  - Generate config pd -> 192.168.31.52:2379 ... Done  - Generate config tikv -> 192.168.31.53:20160 ... Done  - Generate config tikv -> 192.168.31.54:20160 ... Done  - Generate config tikv -> 192.168.31.55:20160 ... Done  - Generate config tikv -> 192.168.31.56:20160 ... Done  - Generate config tidb -> 192.168.31.50:4000 ... Done  - Generate config tiflash -> 192.168.31.57:9000 ... Done  - Generate config prometheus -> 192.168.31.57:9090 ... Done  - Generate config grafana -> 192.168.31.57:3000 ... Done  - Generate config alertmanager -> 192.168.31.57:9093 ... Done+ Reload prometheus and grafana  - Reload prometheus -> 192.168.31.57:9090 ... Done  - Reload grafana -> 192.168.31.57:3000 ... Done+ [ Serial ] - UpdateTopology: cluster=tidb-labScaled cluster `tidb-lab` out successfully

[root@192_168_31_50_TiDB tidb-community-server-v7.1.0-linux-amd64]# tiup cluster display tidb-labtiup is checking updates for component cluster ...Starting component `cluster`: /root/.tiup/components/cluster/v1.12.2/tiup-cluster display tidb-labCluster type:       tidbCluster name:       tidb-labCluster version:    v7.1.0Deploy user:        tidbSSH type:           builtinDashboard URL:      http://192.168.31.51:2379/dashboardGrafana URL:        http://192.168.31.57:3000ID                   Role          Host           Ports                            OS/Arch       Status   Data Dir                      Deploy Dir--                   ----          ----           -----                            -------       ------   --------                      ----------192.168.31.57:9093   alertmanager  192.168.31.57  9093/9094                        linux/x86_64  Up       /tidb-data/alertmanager-9093  /tidb-deploy/alertmanager-9093192.168.31.57:3000   grafana       192.168.31.57  3000                             linux/x86_64  Up       -                             /tidb-deploy/grafana-3000192.168.31.51:2379   pd            192.168.31.51  2379/2380                        linux/x86_64  Up|L|UI  /tidb-data/pd-2379            /tidb-deploy/pd-2379192.168.31.52:2379   pd            192.168.31.52  2379/2380                        linux/x86_64  Up       /tidb-data/pd-2379            /tidb-deploy/pd-2379192.168.31.57:9090   prometheus    192.168.31.57  9090/12020                       linux/x86_64  Up       /tidb-data/prometheus-9090    /tidb-deploy/prometheus-9090192.168.31.50:4000   tidb          192.168.31.50  4000/10080                       linux/x86_64  Up       -                             /tidb-deploy/tidb-4000192.168.31.57:9000   tiflash       192.168.31.57  9000/8123/3930/20170/20292/8234  linux/x86_64  Up       /tidb-data/tiflash-9000       /tidb-deploy/tiflash-9000192.168.31.53:20160  tikv          192.168.31.53  20160/20180                      linux/x86_64  Up       /tidb-data/tikv-20160         /tidb-deploy/tikv-20160192.168.31.54:20160  tikv          192.168.31.54  20160/20180                      linux/x86_64  Up       /tidb-data/tikv-20160         /tidb-deploy/tikv-20160192.168.31.55:20160  tikv          192.168.31.55  20160/20180                      linux/x86_64  Up       /tidb-data/tikv-20160         /tidb-deploy/tikv-20160192.168.31.56:20160  tikv          192.168.31.56  20160/20180                      linux/x86_64  Up       /tidb-data/tikv-20160         /tidb-deploy/tikv-20160Total nodes: 11

[root@192_168_31_50_TiDB tidb-community-toolkit-v7.1.0-linux-amd64]# tar -xvf dumpling-v7.1.0-linux-amd64.tar.gz [root@192_168_31_50_TiDB tidb-community-toolkit-v7.1.0-linux-amd64]# tar -xvf tidb-lightning-v7.1.0-linux-amd64.tar.gz 

[root@192_168_31_50_TiDB tidb-community-toolkit-v7.1.0-linux-amd64]# vim /root/.bash_profile 
# .bash_profile
# Get the aliases and functionsif [ -f ~/.bashrc ]; then        . ~/.bashrcfi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATHexport PATH=/root/.tiup/bin:/tidb-setup/tidb-community-toolkit-v7.1.0-linux-amd64:$PATH

[root@192_168_31_50_TiDB /]# mkdir dumping_erp_db

[root@192_168_31_50_TiDB /]# dumpling -h192.168.31.13 -ujsh_erp -p'P@ssw0rd' -P3306 --filetype sql -t 2  -o /dumpling_erp_db/ -r 20000 -F 256MiB -B jsh_erp