# 2021-06-30-11:17:58+0800 scale up smaregi tidb nodes to r5.4xlarge

- Cause: https://jira.tidbcloud.com/browse/TCOC-107
- Operation:

```
# 1. take a backup of the current cloudprofile
> kubectl get cloudprofile aws > cloudprofile.backup.yaml

# 2. add r5.4xlarge in the cloudprofile
> kubectl edit cloudprofile aws

# 3. take a backup of current shoot spec
> kubectl get shoot -n garden-prod fa365e72 -oyaml > shoot.backup.yaml

# 4. rolling-update the machinedeployment of TiDB (change groups one by one)
> kubectl edit shoot -n garden-prod fa365e72
```

Post actions:

1. add r5.4xlarge spec to our infra repo
2. adjust the cost of the cluster

- Impact: the TiDB pods of the cluster will be rolling-updated and use r5.4xlarge instance
- Recovery operation: rolling-update the node group back to `c5.2xlarge` and apply the backup of cloudprofile
- Time window: 11:45~12:15 CST, 2021-06-30
  - 11:55 scale-up machine of tidb-1
  - 12:07 scale-up machine of tidb-0