# 实验 1：使用 TiUP 部署 TiDB 集群

## 概述

在本实验中，您将安装 TiUP 工具，使用 TiUP 部署 TiDB 集群，检查 TiDB 集群的运行状态，连接到 TiDB server，启动/停止 TiDB 集群，然后查看配置和文件。下图展示了 TiDB 集群的部署拓扑。

  ![60%](https://lab-static.pingcap.com/quick-demo/TiDBClusterDeploymentTopologyExercise_aa_007_20220914.png)

### 实验时长

+ 本实验大约需 60 分钟完成。

> [!TIP]
> 点击 **开始** 启动实验环境。
> 环境准备就绪后，点击底部工具栏中的 **前进** 进入 **模块 1**。
> 然后，按照实验指南的步骤连接到实践环境并开始你的任务。

## 模块 1: 安装 TiUP

### 步骤 1：登录远程 Linux

+ 点击这里 - [终端 1](ssh://monitor1-ssh#1) 打开一个新的终端，连接到为你的实践实验分配的虚拟机。

+ 登录后显示的横幅：

    ```output
     ,     #_
    ~\_  ####_        Amazon Linux 2
    ~~  \_#####\
    ~~     \###|      
    ~~       \#/ ___
    ~~       V~' '->
    ~~~         /    A newer version of Amazon Linux is available!
     ~~._.   _/
        _/ _/       Amazon Linux 2023, GA and supported until 2028-03-15.
      _/m/'           https://aws.amazon.com/linux/amazon-linux-2023/
    ```

### 步骤 2. 查看 `hosts-env.sh` 文件中的 IP 地址

  ```bash
  cat hosts-env.sh
  ```
  ```output
  export HOST_MONITOR1_PRIVATE_IP=10.90.4.19
  export HOST_MONITOR1_PUBLIC_IP=44.234.33.106
  export HOST_CM_PRIVATE_IP=10.90.4.19
  export HOST_CM_PUBLIC_IP=44.234.33.106
  export HOST_PD1_PRIVATE_IP=10.90.1.197
  export HOST_PD1_PUBLIC_IP=18.236.76.37
  export HOST_PD2_PRIVATE_IP=10.90.3.218
  export HOST_PD2_PUBLIC_IP=18.237.226.109
  export HOST_PD3_PRIVATE_IP=10.90.2.84
  export HOST_PD3_PUBLIC_IP=18.237.105.199
  export HOST_DB1_PRIVATE_IP=10.90.3.216
  export HOST_DB1_PUBLIC_IP=34.222.212.46
  export HOST_DB2_PRIVATE_IP=10.90.2.245
  export HOST_DB2_PUBLIC_IP=54.188.31.139
  export HOST_KV1_PRIVATE_IP=10.90.1.94
  export HOST_KV1_PUBLIC_IP=35.87.137.198
  export HOST_KV2_PRIVATE_IP=10.90.2.38
  export HOST_KV2_PUBLIC_IP=35.91.214.228
  export HOST_KV3_PRIVATE_IP=10.90.3.112
  export HOST_KV3_PUBLIC_IP=54.184.160.176
  export HOST_TIFLASH1_PRIVATE_IP=10.90.4.28
  export HOST_TIFLASH1_PUBLIC_IP=34.223.94.92
  ```

### 步骤 3. 在终端环境中设置 IP 地址变量

  ```bash
  source ./hosts-env.sh
  ```

### 步骤 4. 安装 TiUP
  
  ```bash
  curl --proto '=https' --tlsv1.2 -sSf https://tiup-mirrors.pingcap.com/install.sh | sh
  ```
  ```output
  curl --proto '=https' --tlsv1.2 -sSf https://tiup-mirrors.pingcap.com/install.sh | sh
    % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                  Dload  Upload   Total   Spent    Left  Speed
  100 5152k  100 5152k    0     0  14.8M      0 --:--:-- --:--:-- --:--:-- 14.8M
  Successfully set mirror to https://tiup-mirrors.pingcap.com
  Detected shell: bash
  Shell profile:  /home/ec2-user/.bash_profile
  Installed path: /home/ec2-user/.tiup/bin/tiup
  ===============================================
  Have a try:     tiup playground
  ===============================================
  ```

### 步骤 5. 设置 TiUP 环境变量 

  ```bash
  source .bash_profile
  ```

### 步骤 6. 检查 TiUP 集群组件是否安装 

  ```bash
  tiup cluster
  ```
  ```output
  Checking updates for component cluster... Deploy a TiDB cluster for production

  Usage:
  tiup cluster [command]

  Available Commands:
  check       Perform preflight checks for the cluster.
  deploy      Deploy a cluster for production
  start       Start a TiDB cluster
  stop        Stop a TiDB cluster
  restart     Restart a TiDB cluster
  scale-in    Scale in a TiDB cluster
  scale-out   Scale out a TiDB cluster
  destroy     Destroy a specified cluster
  clean       (EXPERIMENTAL) Cleanup a specified cluster
  upgrade     Upgrade a specified TiDB cluster
  display     Display information of a TiDB cluster
  prune       Destroy and remove instances that is in tombstone state
  list        List all clusters
  audit       Show audit log of cluster operation
  import      Import an exist TiDB cluster from TiDB-Ansible
  edit-config Edit TiDB cluster config
  show-config Show TiDB cluster config
  reload      Reload a TiDB cluster's config and restart if needed
  patch       Replace the remote package with a specified package and restart the service
  rename      Rename the cluster
  enable      Enable a TiDB cluster automatically at boot
  disable     Disable automatic enabling of TiDB clusters at boot
  replay      Replay previous operation and skip successed steps
  template    Print topology template
  tls         Enable/Disable TLS between TiDB components
  meta        backup/restore meta information
  rotatessh   rotate ssh keys on all nodes
  help        Help about any command
  completion  Generate the autocompletion script for the specified shell

  Flags:
  -c, --concurrency int     max number of parallel tasks allowed (default 5)
    --format string       (EXPERIMENTAL) The format of output, available values are [default, json] (default "default")
  -h, --help                help for tiup
    --ssh string          (EXPERIMENTAL) The executor type: 'builtin', 'system', 'none'.
    --ssh-timeout uint    Timeout in seconds to connect host via SSH, ignored for operations that don't need an SSH connection. (default 5)
  -v, --version             version for tiup
    --wait-timeout uint   Timeout in seconds to wait for an operation to complete, ignored for operations that don't fit. (default 120)
  -y, --yes                 Skip all confirmations and assumes 'yes'

  Use "tiup cluster help [command]" for more information about a command.
  ```

### 步骤 7. 检查私钥文件的权限是否为只读

  ```bash
  ls -l /home/ec2-user/.ssh/pe-class-key-${LAB:REGION_NAME}.pem
  ```
  ```output
  -r-------- 1 ec2-user ec2-user 1674 May 25 04:09 /home/ec2-user/.ssh/pe-class-key-${LAB:REGION_NAME}.pem
  ```

### 步骤 8. 设置 TiUP 镜像

  ```bash
  tiup mirror set tidb-community-server-7.5.0-linux-amd64
  tiup mirror show
  ```
  ```output
  Successfully set mirror to /home/ec2-user/tidb-community-server-7.5.0-linux-amd64
  /home/ec2-user/tidb-community-server-7.5.0-linux-amd64
  ```

## 模块 2: 部署 TiDB 集群

### 步骤 1: 查看 `solution-topology-ten-nodes.yaml` 

+ `solution-topology-ten-nodes.yaml` 是用于部署 TiDB 集群的 yaml 文件。以下显示的 IP 地址会与您的有所不同。
  
  ```bash
  cat solution-topology-ten-nodes.yaml
  ```
  ```output
  global:
    user: "ec2-user"
    ssh_port: 22
    deploy_dir: "/tidb-deploy"
    data_dir: "/tidb-data"
    arch: "amd64"
  server_configs:
    pd:
        replication.location-labels: ["region","zone","storage-performance"]
        replication.max-replicas: 3
  pd_servers:
    - host: 10.90.2.84
      client_port: 2379
      peer_port: 2380
      advertise_client_addr: "http://54.251.28.224:2379"
      config:
        server.labels:
          region: seattle
          zone: az1
    - host: 10.90.2.134
      client_port: 2379
      peer_port: 2380
      advertise_client_addr: "http://54.179.198.121:2379"
      config:
        server.labels:
          region: seattle
          zone: az2
    - host: 10.90.2.214
      client_port: 2379
      peer_port: 2380
      advertise_client_addr: "http://13.215.194.132:2379"
      config:
        server.labels:
          region: seattle
          zone: az3
  tidb_servers:
    - host: 10.90.2.124
        port: 4000
        status_port: 10080
        deploy_dir: /tidb-deploy/tidb-4000
        log_dir: /tidb-deploy/tidb-4000/log
    - host: 10.90.2.219
        port: 4000
        status_port: 10080
        deploy_dir: /tidb-deploy/tidb-4000
        log_dir: /tidb-deploy/tidb-4000/log
  tikv_servers:
    - host: 10.90.3.239
        port: 20160
        status_port: 20180
        config:
          server.labels:
          region: seattle
          zone: az1
          storage-performance: high
    - host: 10.90.3.119
        port: 20160
        status_port: 20180
        config:
        server.labels:
          region: seattle
          zone: az2
          storage-performance: high
    - host: 10.90.3.181
      port: 20160
      status_port: 20180
      config:
      server.labels:
          region: seattle
          zone: az3
          storage-performance: high
  tiflash_servers:
    - host: 10.90.4.159
      tcp_port: 9000
      flash_service_port: 3930
      deploy_dir: /tidb-deploy/tiflash-9000
      data_dir: /tidb-data/tiflash-9000
      log_dir: /tidb-deploy/tiflash-9000/log
  monitoring_servers:
    - host: 10.90.4.93
  grafana_servers:
    - host: 10.90.4.93
  alertmanager_servers:
    - host: 10.90.4.93
  ```
   
### 步骤 2. 检查节点上是否安装了 `numactl`

+ 所有节点上都应该已安装 `numactl`。我们只需登录到一个 `TiKV` 节点进行检查。

  ```bash
  ssh -i ~/.ssh/pe-class-key-${LAB:REGION_NAME}.pem ec2-user@${HOST_KV1_PRIVATE_IP}
  ```
  ```output
    ,     #_
    ~\_  ####_        Amazon Linux 2
    ~~  \_#####\
    ~~     \###|       
    ~~       \#/ ___
    ~~       V~' '->
      ~~~         /    A newer version of Amazon Linux is available!
        ~~._.   _/
          _/ _/       Amazon Linux 2023, GA and supported until 2028-03-15.
        _/m/'           https://aws.amazon.com/linux/amazon-linux-2023/
  ```

  ```bash
  sudo yum -y install numactl
  ```
  ```output
  Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
  amzn2-core                                                                                                                                 | 3.6 kB  00:00:00     
  60 packages excluded due to repository priority protections
  Package numactl-2.0.9-7.amzn2.x86_64 already installed and latest version
  Nothing to do
  ```

+ 返回控制机: 

  ```bash
  exit
  ```

### 步骤 3. 检查集群部署的系统设置的先决条件

  ```bash
  tiup cluster check ./solution-topology-ten-nodes.yaml \
    --user ec2-user \
    -i /home/ec2-user/.ssh/pe-class-key-${LAB:REGION_NAME}.pem
  ```
  ```output
  + Detect CPU Arch Name
    - Detecting node 10.90.2.90 Arch info ... ⠙ Shell: host=10.90.2.90, sudo=false, command=`uname -m`
    - Detecting node 10.90.2.231 Arch info ... ⠙ Shell: host=10.90.2.231, sudo=false, command=`uname -m`
    - Detecting node 10.90.2.138 Arch info ... ⠙ Shell: host=10.90.2.138, sudo=false, command=`uname -m`
    - Detecting node 10.90.2.242 Arch info ... ⠙ Shell: host=10.90.2.242, sudo=false, command=`uname -m`
  ...
  10.90.2.97   sysctl        Fail    fs.file-max = 376482, should be greater than 1000000
  10.90.2.97   sysctl        Fail    net.core.somaxconn = 4096, should be greater than 32768
  10.90.2.97   sysctl        Fail    net.ipv4.tcp_syncookies = 1, should be 0
  10.90.2.97   sysctl        Fail    vm.swappiness = 60, should be 0
  10.90.2.97   service       Pass    service firewalld not found, ignore
  10.90.2.97   command       Pass    numactl: policy: default
  10.90.2.97   timezone      Pass    time zone is the same as the first PD machine: UTC
  10.90.2.97   os-version    Pass    OS is Amazon Linux 2 
  10.90.2.97   memory        Pass    memory size is 4096MB
  10.90.2.97   limits        Fail    soft limit of 'nofile' for user 'ec2-user' is not set or too low
  10.90.2.97   limits        Fail    hard limit of 'nofile' for user 'ec2-user' is not set or too low
  10.90.2.97   limits        Fail    soft limit of 'stack' for user 'ec2-user' is not set or too low
  10.90.2.97   selinux       Pass    SELinux is disabled
  10.90.2.97   thp           Fail    THP is enabled, please disable it for best performance
  ```

### 步骤 4. 对失败的检查启用自动修复

  ```bash
  tiup cluster check ./solution-topology-ten-nodes.yaml \
    --user ec2-user \
    -i /home/ec2-user/.ssh/pe-class-key-${LAB:REGION_NAME}.pem \
    --apply
  ```
  ```output
  ...
  10.90.3.79   cpu-governor  Warn    Unable to determine current CPU frequency governor policy, auto fixing not supported
  10.90.3.79   sysctl        Fail    will try to set 'fs.file-max = 1000000'
  10.90.3.79   sysctl        Fail    will try to set 'net.core.somaxconn = 32768'
  10.90.3.79   sysctl        Fail    will try to set 'net.ipv4.tcp_syncookies = 0'
  10.90.3.79   sysctl        Fail    will try to set 'vm.swappiness = 0'
  + Try to apply changes to fix failed checks
    - Applying changes on 10.90.2.231 ... Done
    - Applying changes on 10.90.2.138 ... Done
    - Applying changes on 10.90.2.242 ... Done
    - Applying changes on 10.90.2.158 ... Done
    - Applying changes on 10.90.1.56 ... Done
    - Applying changes on 10.90.4.138 ... Done
    - Applying changes on 10.90.2.90 ... Done
    - Applying changes on 10.90.1.169 ... Done
    - Applying changes on 10.90.4.126 ... Done
    - Applying changes on 10.90.2.95 ... Done
  ```

### 步骤 5. 部署一个名为 `tidb-test` 的 TiDB 集群
  ```bash
  tiup cluster deploy tidb-test 7.5.0 ./solution-topology-ten-nodes.yaml \
    --user ec2-user \
    -i /home/ec2-user/.ssh/pe-class-key-${LAB:REGION_NAME}.pem \
    --yes
  ```
  ```output
  + Detect CPU Arch Name
    - Detecting node 10.90.2.90 Arch info ... ⠙ Shell: host=10.90.2.90, sudo=false, command=`uname -m`
    - Detecting node 10.90.2.231 Arch info ... ⠙ Shell: host=10.90.2.231, sudo=false, command=`uname -m`
    - Detecting node 10.90.2.138 Arch info ... ⠙ Shell: host=10.90.2.138, sudo=false, command=`uname -m`
    - Detecting node 10.90.2.242 Arch info ... ⠙ Shell: host=10.90.2.242, sudo=false, command=`uname -m`
  ...
  Cluster `tidb-test` deployed successfully, you can start it with command: `tiup cluster start tidb-test --init`
  ```

## 模块 3: 检查已部署的 TiDB 集群状态

### 步骤 1. 列出由 TiUP 管理的集群

  ```bash
  tiup cluster list
  ```
  ```output
  Name       User      Version  Path                                                     PrivateKey
  ----       ----      -------  ----                                                     ----------
  tidb-test  ec2-user  v7.5.0   /home/ec2-user/.tiup/storage/cluster/clusters/tidb-test  /home/ec2-user/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa
  ```

### 步骤 2. 检查已部署的 TiDB 集群的状态

  ```bash
  tiup cluster display tidb-test
  ```
  ```output
  Cluster type:       tidb
  Cluster name:       tidb-test
  Cluster version:    v7.5.0
  Deploy user:        ec2-user
  SSH type:           builtin
  Grafana URL:        http://10.90.4.138:3000
  ID                 Role          Host         Ports                            OS/Arch       Status  Data Dir                      Deploy Dir
  --                 ----          ----         -----                            -------       ------  --------                      ----------
  10.90.4.138:9093   alertmanager  10.90.4.138  9093/9094                        linux/x86_64  Down    /tidb-data/alertmanager-9093  /tidb-deploy/alertmanager-9093
  10.90.4.138:3000   grafana       10.90.4.138  3000                             linux/x86_64  Down    -                             /tidb-deploy/grafana-3000
  10.90.2.138:2379   pd            10.90.2.138  2379/2380                        linux/x86_64  Down    /tidb-data/pd-2379            /tidb-deploy/pd-2379
  10.90.2.231:2379   pd            10.90.2.231  2379/2380                        linux/x86_64  Down    /tidb-data/pd-2379            /tidb-deploy/pd-2379
  10.90.2.90:2379    pd            10.90.2.90   2379/2380                        linux/x86_64  Down    /tidb-data/pd-2379            /tidb-deploy/pd-2379
  10.90.4.138:9090   prometheus    10.90.4.138  9090/12020                       linux/x86_64  Down    /tidb-data/prometheus-9090    /tidb-deploy/prometheus-9090
  10.90.1.169:4000   tidb          10.90.1.169  4000/10080                       linux/x86_64  Down    -                             /tidb-deploy/tidb-4000
  10.90.1.56:4000    tidb          10.90.1.56   4000/10080                       linux/x86_64  Down    -                             /tidb-deploy/tidb-4000
  10.90.4.126:9000   tiflash       10.90.4.126  9000/8123/3930/20170/20292/8234  linux/x86_64  N/A     /tidb-data/tiflash-9000       /tidb-deploy/tiflash-9000
  10.90.2.158:20160  tikv          10.90.2.158  20160/20180                      linux/x86_64  N/A     /tidb-data/tikv-20160         /tidb-deploy/tikv-20160
  10.90.2.242:20160  tikv          10.90.2.242  20160/20180                      linux/x86_64  N/A     /tidb-data/tikv-20160         /tidb-deploy/tikv-20160
  10.90.2.95:20160   tikv          10.90.2.95   20160/20180                      linux/x86_64  N/A     /tidb-data/tikv-20160         /tidb-deploy/tikv-20160
  Total nodes: 12
  ```

### 步骤 3. 以普通启动方式启动 TiDB 集群

  ```bash
  tiup cluster start tidb-test
  ```
  ```output
  ...
  Started cluster `tidb-test` successfully
  ```

### 步骤 4. 检查已启动的 TiDB 集群的状态

  ```bash
  tiup cluster display tidb-test
  ```
  ```output
  Cluster type:       tidb
  Cluster name:       tidb-test
  Cluster version:    v7.5.0
  Deploy user:        ec2-user
  SSH type:           builtin
  Dashboard URL:      http://34.222.39.121:2379/dashboard
  Grafana URL:        http://10.90.4.138:3000
  ID                 Role          Host         Ports                            OS/Arch       Status  Data Dir                      Deploy Dir
  --                 ----          ----         -----                            -------       ------  --------                      ----------
  10.90.4.138:9093   alertmanager  10.90.4.138  9093/9094                        linux/x86_64  Up      /tidb-data/alertmanager-9093  /tidb-deploy/alertmanager-9093
  10.90.4.138:3000   grafana       10.90.4.138  3000                             linux/x86_64  Up      -                             /tidb-deploy/grafana-3000
  10.90.2.138:2379   pd            10.90.2.138  2379/2380                        linux/x86_64  Up|L    /tidb-data/pd-2379            /tidb-deploy/pd-2379
  10.90.2.231:2379   pd            10.90.2.231  2379/2380                        linux/x86_64  Up      /tidb-data/pd-2379            /tidb-deploy/pd-2379
  10.90.2.90:2379    pd            10.90.2.90   2379/2380                        linux/x86_64  Up      /tidb-data/pd-2379            /tidb-deploy/pd-2379
  10.90.4.138:9090   prometheus    10.90.4.138  9090/12020                       linux/x86_64  Up      /tidb-data/prometheus-9090    /tidb-deploy/prometheus-9090
  10.90.1.169:4000   tidb          10.90.1.169  4000/10080                       linux/x86_64  Up      -                             /tidb-deploy/tidb-4000
  10.90.1.56:4000    tidb          10.90.1.56   4000/10080                       linux/x86_64  Up      -                             /tidb-deploy/tidb-4000
  10.90.4.126:9000   tiflash       10.90.4.126  9000/8123/3930/20170/20292/8234  linux/x86_64  Up      /tidb-data/tiflash-9000       /tidb-deploy/tiflash-9000
  10.90.2.158:20160  tikv          10.90.2.158  20160/20180                      linux/x86_64  Up      /tidb-data/tikv-20160         /tidb-deploy/tikv-20160
  10.90.2.242:20160  tikv          10.90.2.242  20160/20180                      linux/x86_64  Up      /tidb-data/tikv-20160         /tidb-deploy/tikv-20160
  10.90.2.95:20160   tikv          10.90.2.95   20160/20180                      linux/x86_64  Up      /tidb-data/tikv-20160         /tidb-deploy/tikv-20160
  Total nodes: 12
  ```

### 步骤 5. 使用 TiDB PD Dashboard 和 Grafana Prometheus Dashboard 检查集群状态

+ 访问 [TiDB PD Dashboard](http://${LAB:HOST_PD1_PUBLIC_IP}:2379/dashboard) 并检查集群状态。用户名和密码与 TiDB root 用户相同。如果选择标准启动，则密码为空。

   ![60%](https://lab-static.pingcap.com/quick-demo/TiDBDashboard_aa_001_20220615.png)

+ 访问 [Grafana Prometheus Dashboard](http://${LAB:HOST_MONITOR1_PUBLIC_IP}:3000) 并检查集群状态。默认的用户名和密码都是 `admin`。要检查 TiDB 端口状态和负载监控信息，请点击 `tidb-test-Overview`。

   ![40%](https://lab-static.pingcap.com/quick-demo/Grafana_aa_001_20220615.png)

## 模块 4: 连接到 TiDB Server

### 步骤 1. 连接到 TiDB

  ```bash
  mysql -h ${HOST_DB1_PRIVATE_IP} --port 4000 -u root
  ```

### 步骤 2. 查看 TiDB 集群的版本
  ```sql
  SELECT TIDB_VERSION()\G
  ```
  ```output
  *************************** 1. row ***************************
  TIDB_VERSION(): Release Version: v7.5.0
  Edition: Community
  Git Commit Hash: 069631e2ecfedc000ffb92c67207bea81380f020
  Git Branch: heads/refs/tags/v7.5.0
  UTC Build Time: 2023-11-24 08:50:14
  GoVersion: go1.21.3
  Race Enabled: false
  TiKV Min Version: 7.2.0-alpha
  Check Table Before Drop: false
  Store: tikv
  1 row in set (0.00 sec)
  ```

### 步骤 3. 退出到控制机终端

  ```sql
  EXIT;
  ```
  ```output
  Bye
  ```

## 模块 5: 停止 TiDB 集群

### 步骤 1. 停止 TiDB 集群

  ```bash
  tiup cluster stop tidb-test
  ```
  ```output
  Will stop the cluster tidb-test with nodes: , roles: .
  Do you want to continue? [y/N]:(default=N) y
  + [ Serial ] - SSHKeySet: privateKey=/home/ec2-user/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa, publicKey=/home/ec2-user/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa.pub
  + [Parallel] - UserSSH: user=ec2-user, host=10.90.2.95
  + [Parallel] - UserSSH: user=ec2-user, host=10.90.2.90
  + [Parallel] - UserSSH: user=ec2-user, host=10.90.2.158
  + [Parallel] - UserSSH: user=ec2-user, host=10.90.1.169
  + [Parallel] - UserSSH: user=ec2-user, host=10.90.1.56
  + [Parallel] - UserSSH: user=ec2-user, host=10.90.4.126
  + [Parallel] - UserSSH: user=ec2-user, host=10.90.4.138
  + [Parallel] - UserSSH: user=ec2-user, host=10.90.4.138
  + [Parallel] - UserSSH: user=ec2-user, host=10.90.4.138
  + [Parallel] - UserSSH: user=ec2-user, host=10.90.2.138
  + [Parallel] - UserSSH: user=ec2-user, host=10.90.2.242
  + [Parallel] - UserSSH: user=ec2-user, host=10.90.2.231
  + [ Serial ] - StopCluster
  ...
  Stopped cluster `tidb-test` successfully
  ```

## 模块 6: 查看配置文件

### 步骤 1. 查看配置文件的内容

  ```bash
  tiup cluster edit-config tidb-test
  ```
  ```output
  global:
    user: ec2-user
    ssh_port: 22
    ssh_type: builtin
    deploy_dir: /tidb-deploy
    data_dir: /tidb-data
    os: linux
    arch: amd64
    systemd_mode: system
  ...
  alertmanager_servers:
  - host: 10.90.4.138
    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
  ```

+ 输入`:q!`退出终端。

### 步骤 2. 列出 TiDB 配置文件目录中的文件

  ```bash
  ssh -i ~/.ssh/pe-class-key-${LAB:REGION_NAME}.pem ec2-user@${HOST_DB1_PRIVATE_IP} ls -l /tidb-deploy/tidb-4000/
  ```
  ```output
  total 0
  drwxr-xr-x 2 ec2-user ec2-user 25 May 25 04:16 bin
  drwxr-xr-x 2 ec2-user ec2-user 23 May 25 04:16 conf
  drwxr-xr-x 3 ec2-user ec2-user 90 May 25 04:21 log
  drwxr-xr-x 2 ec2-user ec2-user 25 May 25 04:16 scripts
  ```

### 步骤 3. 列出 TiKV 配置文件目录中的文件

  ```bash
  ssh -i ~/.ssh/pe-class-key-${LAB:REGION_NAME}.pem ec2-user@${HOST_KV1_PRIVATE_IP} ls -l /tidb-deploy/
  ```
  ```output
  total 0
  drwxr-xr-x 6 ec2-user ec2-user 55 May 25 04:16 monitor-9100
  drwxr-xr-x 6 ec2-user ec2-user 55 May 25 04:16 tikv-20160
  ```

  ```bash
  ssh -i ~/.ssh/pe-class-key-${LAB:REGION_NAME}.pem ec2-user@${HOST_KV1_PRIVATE_IP} ls -l /tidb-deploy/tikv-20160/
  ```
  ```output
  total 0
  drwxr-xr-x 2 ec2-user ec2-user 25 May 25 04:16 bin
  drwxr-xr-x 2 ec2-user ec2-user 23 May 25 04:16 conf
  drwxr-xr-x 2 ec2-user ec2-user 45 May 25 04:20 log
  drwxr-xr-x 2 ec2-user ec2-user 25 May 25 04:16 scripts
  ```

### 步骤 4. 列出 TiKV 数据文件目录中的文件

  ```bash
  ssh -i ~/.ssh/pe-class-key-${LAB:REGION_NAME}.pem ec2-user@${HOST_KV1_PRIVATE_IP} ls -l /tidb-data/
  ```
  ```output
  total 0
  drwxr-xr-x 2 ec2-user ec2-user   6 May 25 04:16 monitor-9100
  drwxr-xr-x 6 ec2-user ec2-user 164 May 25 04:20 tikv-20160
  ```

  ```bash
  ssh -i ~/.ssh/pe-class-key-${LAB:REGION_NAME}.pem ec2-user@${HOST_KV1_PRIVATE_IP} ls -l /tidb-data/tikv-20160/
  ```
  ```output
  total 1048672
  drwxr-xr-x 2 ec2-user ec2-user        134 May 25 04:20 db
  drwxr-xr-x 4 ec2-user ec2-user         33 May 25 04:20 import
  -rw-r--r-- 1 ec2-user ec2-user      20330 May 25 04:20 last_tikv.toml
  -rw-r--r-- 1 ec2-user ec2-user          0 May 25 04:20 LOCK
  -rw-r--r-- 1 ec2-user ec2-user          0 May 25 04:20 raftdb.info
  drwxr-xr-x 2 ec2-user ec2-user         82 May 25 04:20 raft-engine
  -rw-r--r-- 1 ec2-user ec2-user      75538 May 25 04:20 rocksdb.info
  drwxr-xr-x 2 ec2-user ec2-user          6 May 25 04:21 snap
  -rw-r--r-- 1 ec2-user ec2-user 1073741824 May 25 04:20 space_placeholder_file
  ```

### 步骤 5. 列出 PD 配置文件目录中的文件

  ```bash
  ssh -i ~/.ssh/pe-class-key-${LAB:REGION_NAME}.pem ec2-user@${HOST_PD1_PRIVATE_IP} ls -l /tidb-deploy/
  ```
  ```output
  total 0
  drwxr-xr-x 6 ec2-user ec2-user 55 May 25 04:16 monitor-9100
  drwxr-xr-x 6 ec2-user ec2-user 55 May 25 04:16 pd-2379
  ```

  ```bash
  ssh -i ~/.ssh/pe-class-key-${LAB:REGION_NAME}.pem ec2-user@${HOST_PD1_PRIVATE_IP} ls -l /tidb-deploy/pd-2379/
  ```
  ```output
  total 0
  drwxr-xr-x 2 ec2-user ec2-user 23 May 25 04:16 bin
  drwxr-xr-x 2 ec2-user ec2-user 21 May 25 04:16 conf
  drwxr-xr-x 2 ec2-user ec2-user 41 May 25 04:20 log
  drwxr-xr-x 2 ec2-user ec2-user 23 May 25 04:16 scripts
  ```

### 步骤 6. 列出 PD 数据文件目录中的文件

  ```bash
  ssh -i ~/.ssh/pe-class-key-${LAB:REGION_NAME}.pem ec2-user@${HOST_PD1_PRIVATE_IP} ls -l /tidb-data/
  ```
  ```output
  total 0
  drwxr-xr-x 2 ec2-user ec2-user  6 May 25 04:16 monitor-9100
  drwxr-xr-x 5 ec2-user ec2-user 57 May 25 04:20 pd-2379
  ```

  ```bash
  ssh -i ~/.ssh/pe-class-key-${LAB:REGION_NAME}.pem ec2-user@${HOST_PD1_PRIVATE_IP} ls -l /tidb-data/pd-2379/
  ```
  ```output  
  total 0
  drwxr-xr-x 2 ec2-user ec2-user 85 May 25 04:20 hot-region
  drwx------ 4 ec2-user ec2-user 29 May 25 04:20 member
  drwxr-xr-x 2 ec2-user ec2-user 85 May 25 04:20 region-meta
  ```

## 实验结束
