source commons files source engines files source kubeblocks files `kubectl get namespace | grep ns-aoiok ` `kubectl create namespace ns-aoiok` namespace/ns-aoiok created create namespace ns-aoiok done download kbcli `gh release list --repo apecloud/kbcli --limit 100 | (grep "1.0" || true)` `curl -fsSL https://kubeblocks.io/installer/install_cli.sh | bash -s v1.0.0` Your system is linux_amd64 Installing kbcli ... Downloading ... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 33.6M 100 33.6M 0 0 89.8M 0 --:--:-- --:--:-- --:--:-- 89.8M kbcli installed successfully. Kubernetes: v1.32.5-eks-5d4a308 KubeBlocks: 1.0.0 kbcli: 1.0.0 Make sure your docker service is running and begin your journey with kbcli: kbcli playground init For more information on how to get started, please visit: https://kubeblocks.io download kbcli v1.0.0 done Kubernetes: v1.32.5-eks-5d4a308 KubeBlocks: 1.0.0 kbcli: 1.0.0 Kubernetes Env: v1.32.5-eks-5d4a308 check snapshot controller check snapshot controller done eks default-vsc found POD_RESOURCES: No resources found found default storage class: gp3 KubeBlocks version is:1.0.0 skip upgrade KubeBlocks current KubeBlocks version: 1.0.0 Error: no repositories to show helm repo add chaos-mesh https://charts.chaos-mesh.org "chaos-mesh" has been added to your repositories add helm chart repo chaos-mesh success chaos mesh already installed check component definition set component name:tidb set component version set component version:tidb set service versions:8.4.0,7.5.2,7.1.5,6.5.12 set service versions sorted:6.5.12,7.1.5,7.5.2,8.4.0 set tidb component definition set tidb component definition tidb-pd-7-1.0.0-alpha.0 set replicas first:2,6.5.12|2,7.1.5|2,7.5.2|2,8.4.0 set replicas third:2,7.1.5 set replicas fourth:2,7.1.5 set minimum cmpv service version set minimum cmpv service version replicas:2,7.1.5 REPORT_COUNT:1 CLUSTER_TOPOLOGY: set cluster topology: cluster set tidb component definition set tidb component definition tidb-pd-7-1.0.0-alpha.0 LIMIT_CPU:0.5 LIMIT_MEMORY:3 storage size: 20 No resources found in ns-aoiok namespace. termination_policy:DoNotTerminate create 2 replica DoNotTerminate tidb cluster check component definition set component definition by component version check cmpd by labels set component definition1: tidb-7-1.0.0-alpha.0 by component version:tidb apiVersion: apps.kubeblocks.io/v1 kind: Cluster metadata: name: tidb-hdfezd namespace: ns-aoiok spec: clusterDef: tidb topology: cluster terminationPolicy: DoNotTerminate componentSpecs: - name: tidb replicas: 2 serviceVersion: 7.1.5 disableExporter: false resources: requests: cpu: 500m memory: 3Gi limits: cpu: 500m memory: 3Gi - name: tikv replicas: 1 serviceVersion: 7.1.5 disableExporter: false resources: requests: cpu: 500m memory: 3Gi limits: cpu: 500m memory: 3Gi volumeClaimTemplates: - name: data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: tidb-pd replicas: 1 serviceVersion: 7.1.5 disableExporter: false resources: requests: cpu: 500m memory: 3Gi limits: cpu: 500m memory: 3Gi volumeClaimTemplates: - name: data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi `kubectl apply -f test_create_tidb-hdfezd.yaml` cluster.apps.kubeblocks.io/tidb-hdfezd created apply test_create_tidb-hdfezd.yaml Success `rm -rf test_create_tidb-hdfezd.yaml` check cluster status `kbcli cluster list tidb-hdfezd --show-labels --namespace ns-aoiok ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS tidb-hdfezd ns-aoiok tidb DoNotTerminate May 28,2025 11:38 UTC+0800 clusterdefinition.kubeblocks.io/name=tidb cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances tidb-hdfezd --namespace ns-aoiok ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME tidb-hdfezd-tidb-0 ns-aoiok tidb-hdfezd tidb Running us-west-2a 500m / 500m 3Gi / 3Gi ip-172-31-5-250.us-west-2.compute.internal/172.31.5.250 May 28,2025 11:41 UTC+0800 tidb-hdfezd-tidb-1 ns-aoiok tidb-hdfezd tidb Running us-west-2a 500m / 500m 3Gi / 3Gi ip-172-31-12-133.us-west-2.compute.internal/172.31.12.133 May 28,2025 11:41 UTC+0800 tidb-hdfezd-tidb-pd-0 ns-aoiok tidb-hdfezd tidb-pd Running leader us-west-2a 500m / 500m 3Gi / 3Gi data:20Gi ip-172-31-12-152.us-west-2.compute.internal/172.31.12.152 May 28,2025 11:39 UTC+0800 tidb-hdfezd-tikv-0 ns-aoiok tidb-hdfezd tikv Running us-west-2a 500m / 500m 3Gi / 3Gi data:20Gi ip-172-31-11-7.us-west-2.compute.internal/172.31.11.7 May 28,2025 11:40 UTC+0800 check pod status done connect unsupported engine type: tidb tidb-7-1.0.0-alpha.0 `kubectl get secrets -l app.kubernetes.io/instance=tidb-hdfezd` set secret: tidb-hdfezd-tidb-account-root `kubectl get secrets tidb-hdfezd-tidb-account-root -o jsonpath="***.data.username***"` `kubectl get secrets tidb-hdfezd-tidb-account-root -o jsonpath="***.data.password***"` `kubectl get secrets tidb-hdfezd-tidb-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:4g2gogT21tFlbp1e;DB_PORT:4000;DB_DATABASE: check pod tidb-hdfezd-tidb-0 container_name tidb exist password 4g2gogT21tFlbp1e check pod tidb-hdfezd-tidb-0 container_name slowlog exist password 4g2gogT21tFlbp1e check pod tidb-hdfezd-tidb-0 container_name kbagent exist password 4g2gogT21tFlbp1e No container logs contain secret password. describe cluster `kbcli cluster describe tidb-hdfezd --namespace ns-aoiok ` Name: tidb-hdfezd Created Time: May 28,2025 11:38 UTC+0800 NAMESPACE CLUSTER-DEFINITION TOPOLOGY STATUS TERMINATION-POLICY ns-aoiok tidb cluster Running DoNotTerminate Endpoints: COMPONENT INTERNAL EXTERNAL tidb-pd tidb-hdfezd-tidb-pd.ns-aoiok.svc.cluster.local:2379 tidb-hdfezd-tidb-pd.ns-aoiok.svc.cluster.local:2380 tikv tidb-hdfezd-tikv.ns-aoiok.svc.cluster.local:20160 tidb-hdfezd-tikv.ns-aoiok.svc.cluster.local:20180 tidb tidb-hdfezd-tidb.ns-aoiok.svc.cluster.local:4000 tidb-hdfezd-tidb.ns-aoiok.svc.cluster.local:10080 Topology: COMPONENT SERVICE-VERSION INSTANCE ROLE STATUS AZ NODE CREATED-TIME tidb 7.1.5 tidb-hdfezd-tidb-0 Running us-west-2a ip-172-31-5-250.us-west-2.compute.internal/172.31.5.250 May 28,2025 11:41 UTC+0800 tidb 7.1.5 tidb-hdfezd-tidb-1 Running us-west-2a ip-172-31-12-133.us-west-2.compute.internal/172.31.12.133 May 28,2025 11:41 UTC+0800 tidb-pd 7.1.5 tidb-hdfezd-tidb-pd-0 leader Running us-west-2a ip-172-31-12-152.us-west-2.compute.internal/172.31.12.152 May 28,2025 11:39 UTC+0800 tikv 7.1.5 tidb-hdfezd-tikv-0 Running us-west-2a ip-172-31-11-7.us-west-2.compute.internal/172.31.11.7 May 28,2025 11:40 UTC+0800 Resources Allocation: COMPONENT INSTANCE-TEMPLATE CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS tidb-pd 500m / 500m 3Gi / 3Gi data:20Gi kb-default-sc tikv 500m / 500m 3Gi / 3Gi data:20Gi kb-default-sc tidb 500m / 500m 3Gi / 3Gi Images: COMPONENT COMPONENT-DEFINITION IMAGE tidb-pd tidb-pd-7-1.0.0-alpha.0 docker.io/apecloud/pd:v7.1.5 docker.io/apecloud/kubeblocks-tools:1.0.0 tikv tikv-7-1.0.0-alpha.0 docker.io/apecloud/tikv:v7.1.5 docker.io/apecloud/pd:v7.1.5 tidb tidb-7-1.0.0-alpha.0 docker.io/apecloud/tidb:v7.1.5 docker.io/apecloud/busybox:1.35 docker.io/apecloud/alpine-mysql-client:15.1 Show cluster events: kbcli cluster list-events -n ns-aoiok tidb-hdfezd `kbcli cluster label tidb-hdfezd app.kubernetes.io/instance- --namespace ns-aoiok ` label "app.kubernetes.io/instance" not found. `kbcli cluster label tidb-hdfezd app.kubernetes.io/instance=tidb-hdfezd --namespace ns-aoiok ` `kbcli cluster label tidb-hdfezd --list --namespace ns-aoiok ` NAME NAMESPACE LABELS tidb-hdfezd ns-aoiok app.kubernetes.io/instance=tidb-hdfezd clusterdefinition.kubeblocks.io/name=tidb label cluster app.kubernetes.io/instance=tidb-hdfezd Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=tidb-hdfezd --namespace ns-aoiok ` `kbcli cluster label tidb-hdfezd --list --namespace ns-aoiok ` NAME NAMESPACE LABELS tidb-hdfezd ns-aoiok app.kubernetes.io/instance=tidb-hdfezd case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=tidb label cluster case.name=kbcli.test1 Success `kbcli cluster label tidb-hdfezd case.name=kbcli.test2 --overwrite --namespace ns-aoiok ` `kbcli cluster label tidb-hdfezd --list --namespace ns-aoiok ` NAME NAMESPACE LABELS tidb-hdfezd ns-aoiok app.kubernetes.io/instance=tidb-hdfezd case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=tidb label cluster case.name=kbcli.test2 Success `kbcli cluster label tidb-hdfezd case.name- --namespace ns-aoiok ` `kbcli cluster label tidb-hdfezd --list --namespace ns-aoiok ` NAME NAMESPACE LABELS tidb-hdfezd ns-aoiok app.kubernetes.io/instance=tidb-hdfezd clusterdefinition.kubeblocks.io/name=tidb delete cluster label case.name Success cluster connect create mysql-client pod pod_mysql_client `kubectl run --namespace ns-aoiok tidb-hdfezd-mysql-client --restart='Never' --image docker.io/apecloud/mysql-client:latest --command -- sleep infinity` pod/tidb-hdfezd-mysql-client created check pod status pod_status:NAME READY STATUS RESTARTS AGE tidb-hdfezd-mysql-client 0/1 ContainerCreating 0 1s check pod tidb-hdfezd-mysql-client status done `kubectl wait --for=condition=Ready pod tidb-hdfezd-mysql-client --namespace ns-aoiok` pod/tidb-hdfezd-mysql-client condition met pod_status:NAME READY STATUS RESTARTS AGE tidb-hdfezd-mysql-client 1/1 Running 0 6s `kubectl get secrets -l app.kubernetes.io/instance=tidb-hdfezd` set secret: tidb-hdfezd-tidb-account-root `kubectl get secrets tidb-hdfezd-tidb-account-root -o jsonpath="***.data.username***"` `kubectl get secrets tidb-hdfezd-tidb-account-root -o jsonpath="***.data.password***"` `kubectl get secrets tidb-hdfezd-tidb-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:4g2gogT21tFlbp1e;DB_PORT:4000;DB_DATABASE: `echo "echo 'select 1;' | mysql -htidb-hdfezd-tidb.ns-aoiok.svc.cluster.local -P4000 -uroot -p'4g2gogT21tFlbp1e'" | kubectl exec -it tidb-hdfezd-mysql-client --namespace ns-aoiok -- sh ` Unable to use a TTY - input is not a terminal or the right kind of file 1 1 connect cluster Success `kubectl delete pod tidb-hdfezd-mysql-client --force --namespace ns-aoiok ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. pod "tidb-hdfezd-mysql-client" force deleted check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale tidb-hdfezd --auto-approve --force=true --components tidb --cpu 600m --memory 3.1Gi --namespace ns-aoiok ` OpsRequest tidb-hdfezd-verticalscaling-2nlpk created successfully, you can view the progress: kbcli cluster describe-ops tidb-hdfezd-verticalscaling-2nlpk -n ns-aoiok check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-verticalscaling-2nlpk ns-aoiok VerticalScaling tidb-hdfezd tidb Running 0/2 May 28,2025 11:42 UTC+0800 check cluster status `kbcli cluster list tidb-hdfezd --show-labels --namespace ns-aoiok ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS tidb-hdfezd ns-aoiok tidb DoNotTerminate Updating May 28,2025 11:38 UTC+0800 app.kubernetes.io/instance=tidb-hdfezd,clusterdefinition.kubeblocks.io/name=tidb cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances tidb-hdfezd --namespace ns-aoiok ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME tidb-hdfezd-tidb-0 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-6-100.us-west-2.compute.internal/172.31.6.100 May 28,2025 11:43 UTC+0800 tidb-hdfezd-tidb-1 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-12-133.us-west-2.compute.internal/172.31.12.133 May 28,2025 11:43 UTC+0800 tidb-hdfezd-tidb-pd-0 ns-aoiok tidb-hdfezd tidb-pd Running leader us-west-2a 500m / 500m 3Gi / 3Gi data:20Gi ip-172-31-12-152.us-west-2.compute.internal/172.31.12.152 May 28,2025 11:39 UTC+0800 tidb-hdfezd-tikv-0 ns-aoiok tidb-hdfezd tikv Running us-west-2a 500m / 500m 3Gi / 3Gi data:20Gi ip-172-31-11-7.us-west-2.compute.internal/172.31.11.7 May 28,2025 11:40 UTC+0800 check pod status done connect unsupported engine type: tidb tidb-7-1.0.0-alpha.0 check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-verticalscaling-2nlpk ns-aoiok VerticalScaling tidb-hdfezd tidb Succeed 2/2 May 28,2025 11:42 UTC+0800 check ops status done ops_status:tidb-hdfezd-verticalscaling-2nlpk ns-aoiok VerticalScaling tidb-hdfezd tidb Succeed 2/2 May 28,2025 11:42 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations tidb-hdfezd-verticalscaling-2nlpk --namespace ns-aoiok ` opsrequest.operations.kubeblocks.io/tidb-hdfezd-verticalscaling-2nlpk patched `kbcli cluster delete-ops --name tidb-hdfezd-verticalscaling-2nlpk --force --auto-approve --namespace ns-aoiok ` OpsRequest tidb-hdfezd-verticalscaling-2nlpk deleted check component tidb exists `kubectl get components -l app.kubernetes.io/instance=tidb-hdfezd,apps.kubeblocks.io/component-name=tidb --namespace ns-aoiok | (grep "tidb" || true )` check component tikv exists `kubectl get components -l app.kubernetes.io/instance=tidb-hdfezd,apps.kubeblocks.io/component-name=tikv --namespace ns-aoiok | (grep "tikv" || true )` cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart tidb-hdfezd --auto-approve --force=true --components tidb,tikv --namespace ns-aoiok ` OpsRequest tidb-hdfezd-restart-fpbkq created successfully, you can view the progress: kbcli cluster describe-ops tidb-hdfezd-restart-fpbkq -n ns-aoiok check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-restart-fpbkq ns-aoiok Restart tidb-hdfezd tidb,tikv Running 0/3 May 28,2025 11:44 UTC+0800 check cluster status `kbcli cluster list tidb-hdfezd --show-labels --namespace ns-aoiok ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS tidb-hdfezd ns-aoiok tidb DoNotTerminate Updating May 28,2025 11:38 UTC+0800 app.kubernetes.io/instance=tidb-hdfezd,clusterdefinition.kubeblocks.io/name=tidb cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances tidb-hdfezd --namespace ns-aoiok ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME tidb-hdfezd-tidb-0 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-6-100.us-west-2.compute.internal/172.31.6.100 May 28,2025 11:45 UTC+0800 tidb-hdfezd-tidb-1 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-12-133.us-west-2.compute.internal/172.31.12.133 May 28,2025 11:44 UTC+0800 tidb-hdfezd-tidb-pd-0 ns-aoiok tidb-hdfezd tidb-pd Running leader us-west-2a 500m / 500m 3Gi / 3Gi data:20Gi ip-172-31-12-152.us-west-2.compute.internal/172.31.12.152 May 28,2025 11:39 UTC+0800 tidb-hdfezd-tikv-0 ns-aoiok tidb-hdfezd tikv Running us-west-2a 500m / 500m 3Gi / 3Gi data:20Gi ip-172-31-11-7.us-west-2.compute.internal/172.31.11.7 May 28,2025 11:45 UTC+0800 check pod status done connect unsupported engine type: tidb tidb-7-1.0.0-alpha.0 check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-restart-fpbkq ns-aoiok Restart tidb-hdfezd tidb,tikv Succeed 3/3 May 28,2025 11:44 UTC+0800 check ops status done ops_status:tidb-hdfezd-restart-fpbkq ns-aoiok Restart tidb-hdfezd tidb,tikv Succeed 3/3 May 28,2025 11:44 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations tidb-hdfezd-restart-fpbkq --namespace ns-aoiok ` opsrequest.operations.kubeblocks.io/tidb-hdfezd-restart-fpbkq patched `kbcli cluster delete-ops --name tidb-hdfezd-restart-fpbkq --force --auto-approve --namespace ns-aoiok ` OpsRequest tidb-hdfezd-restart-fpbkq deleted check component tidb-pd exists `kubectl get components -l app.kubernetes.io/instance=tidb-hdfezd,apps.kubeblocks.io/component-name=tidb-pd --namespace ns-aoiok | (grep "tidb-pd" || true )` check component tikv exists `kubectl get components -l app.kubernetes.io/instance=tidb-hdfezd,apps.kubeblocks.io/component-name=tikv --namespace ns-aoiok | (grep "tikv" || true )` `kubectl get pvc -l app.kubernetes.io/instance=tidb-hdfezd,apps.kubeblocks.io/component-name=tidb-pd,tikv,apps.kubeblocks.io/vct-name=data --namespace ns-aoiok ` No resources found in ns-aoiok namespace. tidb-hdfezd tidb-pd,tikv data pvc is empty cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in tidb-hdfezd namespace. `kbcli cluster volume-expand tidb-hdfezd --auto-approve --force=true --components tidb-pd,tikv --volume-claim-templates data --storage 22Gi --namespace ns-aoiok ` OpsRequest tidb-hdfezd-volumeexpansion-pjwfk created successfully, you can view the progress: kbcli cluster describe-ops tidb-hdfezd-volumeexpansion-pjwfk -n ns-aoiok check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-volumeexpansion-pjwfk ns-aoiok VolumeExpansion tidb-hdfezd tidb-pd,tikv Running 0/2 May 28,2025 11:46 UTC+0800 check cluster status `kbcli cluster list tidb-hdfezd --show-labels --namespace ns-aoiok ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS tidb-hdfezd ns-aoiok tidb DoNotTerminate Updating May 28,2025 11:38 UTC+0800 app.kubernetes.io/instance=tidb-hdfezd,clusterdefinition.kubeblocks.io/name=tidb cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances tidb-hdfezd --namespace ns-aoiok ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME tidb-hdfezd-tidb-0 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-6-100.us-west-2.compute.internal/172.31.6.100 May 28,2025 11:45 UTC+0800 tidb-hdfezd-tidb-1 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-12-133.us-west-2.compute.internal/172.31.12.133 May 28,2025 11:44 UTC+0800 tidb-hdfezd-tidb-pd-0 ns-aoiok tidb-hdfezd tidb-pd Running leader us-west-2a 500m / 500m 3Gi / 3Gi data:22Gi ip-172-31-12-152.us-west-2.compute.internal/172.31.12.152 May 28,2025 11:39 UTC+0800 tidb-hdfezd-tikv-0 ns-aoiok tidb-hdfezd tikv Running us-west-2a 500m / 500m 3Gi / 3Gi data:22Gi ip-172-31-11-7.us-west-2.compute.internal/172.31.11.7 May 28,2025 11:45 UTC+0800 check pod status done connect unsupported engine type: tidb tidb-7-1.0.0-alpha.0 No resources found in tidb-hdfezd namespace. check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-volumeexpansion-pjwfk ns-aoiok VolumeExpansion tidb-hdfezd tidb-pd,tikv Succeed 2/2 May 28,2025 11:46 UTC+0800 check ops status done ops_status:tidb-hdfezd-volumeexpansion-pjwfk ns-aoiok VolumeExpansion tidb-hdfezd tidb-pd,tikv Succeed 2/2 May 28,2025 11:46 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations tidb-hdfezd-volumeexpansion-pjwfk --namespace ns-aoiok ` opsrequest.operations.kubeblocks.io/tidb-hdfezd-volumeexpansion-pjwfk patched `kbcli cluster delete-ops --name tidb-hdfezd-volumeexpansion-pjwfk --force --auto-approve --namespace ns-aoiok ` OpsRequest tidb-hdfezd-volumeexpansion-pjwfk deleted cluster tidb scale-out check cluster status before ops check cluster status done cluster_status:Running No resources found in tidb-hdfezd namespace. `kbcli cluster scale-out tidb-hdfezd --auto-approve --force=true --components tidb --replicas 1 --namespace ns-aoiok ` OpsRequest tidb-hdfezd-horizontalscaling-b2bvt created successfully, you can view the progress: kbcli cluster describe-ops tidb-hdfezd-horizontalscaling-b2bvt -n ns-aoiok check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-horizontalscaling-b2bvt ns-aoiok HorizontalScaling tidb-hdfezd tidb Running 0/1 May 28,2025 11:48 UTC+0800 check cluster status `kbcli cluster list tidb-hdfezd --show-labels --namespace ns-aoiok ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS tidb-hdfezd ns-aoiok tidb DoNotTerminate Updating May 28,2025 11:38 UTC+0800 app.kubernetes.io/instance=tidb-hdfezd,clusterdefinition.kubeblocks.io/name=tidb cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances tidb-hdfezd --namespace ns-aoiok ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME tidb-hdfezd-tidb-0 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-6-100.us-west-2.compute.internal/172.31.6.100 May 28,2025 11:45 UTC+0800 tidb-hdfezd-tidb-1 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-12-133.us-west-2.compute.internal/172.31.12.133 May 28,2025 11:44 UTC+0800 tidb-hdfezd-tidb-2 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-5-12.us-west-2.compute.internal/172.31.5.12 May 28,2025 11:48 UTC+0800 tidb-hdfezd-tidb-pd-0 ns-aoiok tidb-hdfezd tidb-pd Running leader us-west-2a 500m / 500m 3Gi / 3Gi data:22Gi ip-172-31-12-152.us-west-2.compute.internal/172.31.12.152 May 28,2025 11:39 UTC+0800 tidb-hdfezd-tikv-0 ns-aoiok tidb-hdfezd tikv Running us-west-2a 500m / 500m 3Gi / 3Gi data:22Gi ip-172-31-11-7.us-west-2.compute.internal/172.31.11.7 May 28,2025 11:45 UTC+0800 check pod status done connect unsupported engine type: tidb tidb-7-1.0.0-alpha.0 No resources found in tidb-hdfezd namespace. check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-horizontalscaling-b2bvt ns-aoiok HorizontalScaling tidb-hdfezd tidb Succeed 1/1 May 28,2025 11:48 UTC+0800 check ops status done ops_status:tidb-hdfezd-horizontalscaling-b2bvt ns-aoiok HorizontalScaling tidb-hdfezd tidb Succeed 1/1 May 28,2025 11:48 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations tidb-hdfezd-horizontalscaling-b2bvt --namespace ns-aoiok ` opsrequest.operations.kubeblocks.io/tidb-hdfezd-horizontalscaling-b2bvt patched `kbcli cluster delete-ops --name tidb-hdfezd-horizontalscaling-b2bvt --force --auto-approve --namespace ns-aoiok ` OpsRequest tidb-hdfezd-horizontalscaling-b2bvt deleted cluster tidb scale-in check cluster status before ops check cluster status done cluster_status:Running No resources found in tidb-hdfezd namespace. `kbcli cluster scale-in tidb-hdfezd --auto-approve --force=true --components tidb --replicas 1 --namespace ns-aoiok ` OpsRequest tidb-hdfezd-horizontalscaling-c799j created successfully, you can view the progress: kbcli cluster describe-ops tidb-hdfezd-horizontalscaling-c799j -n ns-aoiok check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-horizontalscaling-c799j ns-aoiok HorizontalScaling tidb-hdfezd tidb Running 0/1 May 28,2025 11:49 UTC+0800 check cluster status `kbcli cluster list tidb-hdfezd --show-labels --namespace ns-aoiok ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS tidb-hdfezd ns-aoiok tidb DoNotTerminate Updating May 28,2025 11:38 UTC+0800 app.kubernetes.io/instance=tidb-hdfezd,clusterdefinition.kubeblocks.io/name=tidb cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances tidb-hdfezd --namespace ns-aoiok ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME tidb-hdfezd-tidb-0 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-6-100.us-west-2.compute.internal/172.31.6.100 May 28,2025 11:45 UTC+0800 tidb-hdfezd-tidb-1 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-12-133.us-west-2.compute.internal/172.31.12.133 May 28,2025 11:44 UTC+0800 tidb-hdfezd-tidb-pd-0 ns-aoiok tidb-hdfezd tidb-pd Running leader us-west-2a 500m / 500m 3Gi / 3Gi data:22Gi ip-172-31-12-152.us-west-2.compute.internal/172.31.12.152 May 28,2025 11:39 UTC+0800 tidb-hdfezd-tikv-0 ns-aoiok tidb-hdfezd tikv Running us-west-2a 500m / 500m 3Gi / 3Gi data:22Gi ip-172-31-11-7.us-west-2.compute.internal/172.31.11.7 May 28,2025 11:45 UTC+0800 check pod status done connect unsupported engine type: tidb tidb-7-1.0.0-alpha.0 No resources found in tidb-hdfezd namespace. check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-horizontalscaling-c799j ns-aoiok HorizontalScaling tidb-hdfezd tidb Succeed 1/1 May 28,2025 11:49 UTC+0800 check ops status done ops_status:tidb-hdfezd-horizontalscaling-c799j ns-aoiok HorizontalScaling tidb-hdfezd tidb Succeed 1/1 May 28,2025 11:49 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations tidb-hdfezd-horizontalscaling-c799j --namespace ns-aoiok ` opsrequest.operations.kubeblocks.io/tidb-hdfezd-horizontalscaling-c799j patched `kbcli cluster delete-ops --name tidb-hdfezd-horizontalscaling-c799j --force --auto-approve --namespace ns-aoiok ` OpsRequest tidb-hdfezd-horizontalscaling-c799j deleted check component tidb-pd exists `kubectl get components -l app.kubernetes.io/instance=tidb-hdfezd,apps.kubeblocks.io/component-name=tidb-pd --namespace ns-aoiok | (grep "tidb-pd" || true )` check component tikv exists `kubectl get components -l app.kubernetes.io/instance=tidb-hdfezd,apps.kubeblocks.io/component-name=tikv --namespace ns-aoiok | (grep "tikv" || true )` check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale tidb-hdfezd --auto-approve --force=true --components tidb-pd,tikv --cpu 600m --memory 3.1Gi --namespace ns-aoiok ` OpsRequest tidb-hdfezd-verticalscaling-njzc6 created successfully, you can view the progress: kbcli cluster describe-ops tidb-hdfezd-verticalscaling-njzc6 -n ns-aoiok check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-verticalscaling-njzc6 ns-aoiok VerticalScaling tidb-hdfezd tidb-pd,tikv Running 0/2 May 28,2025 11:49 UTC+0800 check cluster status `kbcli cluster list tidb-hdfezd --show-labels --namespace ns-aoiok ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS tidb-hdfezd ns-aoiok tidb DoNotTerminate Updating May 28,2025 11:38 UTC+0800 app.kubernetes.io/instance=tidb-hdfezd,clusterdefinition.kubeblocks.io/name=tidb cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances tidb-hdfezd --namespace ns-aoiok ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME tidb-hdfezd-tidb-0 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-6-100.us-west-2.compute.internal/172.31.6.100 May 28,2025 11:45 UTC+0800 tidb-hdfezd-tidb-1 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-12-133.us-west-2.compute.internal/172.31.12.133 May 28,2025 11:44 UTC+0800 tidb-hdfezd-tidb-pd-0 ns-aoiok tidb-hdfezd tidb-pd Running leader us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-12-152.us-west-2.compute.internal/172.31.12.152 May 28,2025 11:50 UTC+0800 tidb-hdfezd-tikv-0 ns-aoiok tidb-hdfezd tikv Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-11-7.us-west-2.compute.internal/172.31.11.7 May 28,2025 11:49 UTC+0800 check pod status done connect unsupported engine type: tidb tidb-7-1.0.0-alpha.0 check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-verticalscaling-njzc6 ns-aoiok VerticalScaling tidb-hdfezd tidb-pd,tikv Succeed 2/2 May 28,2025 11:49 UTC+0800 check ops status done ops_status:tidb-hdfezd-verticalscaling-njzc6 ns-aoiok VerticalScaling tidb-hdfezd tidb-pd,tikv Succeed 2/2 May 28,2025 11:49 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations tidb-hdfezd-verticalscaling-njzc6 --namespace ns-aoiok ` opsrequest.operations.kubeblocks.io/tidb-hdfezd-verticalscaling-njzc6 patched `kbcli cluster delete-ops --name tidb-hdfezd-verticalscaling-njzc6 --force --auto-approve --namespace ns-aoiok ` OpsRequest tidb-hdfezd-verticalscaling-njzc6 deleted check component tikv exists `kubectl get components -l app.kubernetes.io/instance=tidb-hdfezd,apps.kubeblocks.io/component-name=tikv --namespace ns-aoiok | (grep "tikv" || true )` cluster tikv scale-out check cluster status before ops check cluster status done cluster_status:Running No resources found in tidb-hdfezd namespace. `kbcli cluster scale-out tidb-hdfezd --auto-approve --force=true --components tikv --replicas 1 --namespace ns-aoiok ` OpsRequest tidb-hdfezd-horizontalscaling-gqp9m created successfully, you can view the progress: kbcli cluster describe-ops tidb-hdfezd-horizontalscaling-gqp9m -n ns-aoiok check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-horizontalscaling-gqp9m ns-aoiok HorizontalScaling tidb-hdfezd tikv Running 0/1 May 28,2025 11:51 UTC+0800 check cluster status `kbcli cluster list tidb-hdfezd --show-labels --namespace ns-aoiok ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS tidb-hdfezd ns-aoiok tidb DoNotTerminate Updating May 28,2025 11:38 UTC+0800 app.kubernetes.io/instance=tidb-hdfezd,clusterdefinition.kubeblocks.io/name=tidb cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances tidb-hdfezd --namespace ns-aoiok ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME tidb-hdfezd-tidb-0 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-6-100.us-west-2.compute.internal/172.31.6.100 May 28,2025 11:45 UTC+0800 tidb-hdfezd-tidb-1 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-12-133.us-west-2.compute.internal/172.31.12.133 May 28,2025 11:44 UTC+0800 tidb-hdfezd-tidb-pd-0 ns-aoiok tidb-hdfezd tidb-pd Running leader us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-12-152.us-west-2.compute.internal/172.31.12.152 May 28,2025 11:50 UTC+0800 tidb-hdfezd-tikv-0 ns-aoiok tidb-hdfezd tikv Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-11-7.us-west-2.compute.internal/172.31.11.7 May 28,2025 11:49 UTC+0800 tidb-hdfezd-tikv-1 ns-aoiok tidb-hdfezd tikv Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-13-212.us-west-2.compute.internal/172.31.13.212 May 28,2025 11:51 UTC+0800 check pod status done connect unsupported engine type: tidb tidb-7-1.0.0-alpha.0 No resources found in tidb-hdfezd namespace. check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-horizontalscaling-gqp9m ns-aoiok HorizontalScaling tidb-hdfezd tikv Succeed 1/1 May 28,2025 11:51 UTC+0800 check ops status done ops_status:tidb-hdfezd-horizontalscaling-gqp9m ns-aoiok HorizontalScaling tidb-hdfezd tikv Succeed 1/1 May 28,2025 11:51 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations tidb-hdfezd-horizontalscaling-gqp9m --namespace ns-aoiok ` opsrequest.operations.kubeblocks.io/tidb-hdfezd-horizontalscaling-gqp9m patched `kbcli cluster delete-ops --name tidb-hdfezd-horizontalscaling-gqp9m --force --auto-approve --namespace ns-aoiok ` OpsRequest tidb-hdfezd-horizontalscaling-gqp9m deleted cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart tidb-hdfezd --auto-approve --force=true --namespace ns-aoiok ` OpsRequest tidb-hdfezd-restart-xwk9l created successfully, you can view the progress: kbcli cluster describe-ops tidb-hdfezd-restart-xwk9l -n ns-aoiok check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-restart-xwk9l ns-aoiok Restart tidb-hdfezd tidb-pd,tikv,tidb Running 0/5 May 28,2025 11:52 UTC+0800 check cluster status `kbcli cluster list tidb-hdfezd --show-labels --namespace ns-aoiok ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS tidb-hdfezd ns-aoiok tidb DoNotTerminate Updating May 28,2025 11:38 UTC+0800 app.kubernetes.io/instance=tidb-hdfezd,clusterdefinition.kubeblocks.io/name=tidb cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances tidb-hdfezd --namespace ns-aoiok ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME tidb-hdfezd-tidb-0 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-6-100.us-west-2.compute.internal/172.31.6.100 May 28,2025 11:53 UTC+0800 tidb-hdfezd-tidb-1 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-12-133.us-west-2.compute.internal/172.31.12.133 May 28,2025 11:52 UTC+0800 tidb-hdfezd-tidb-pd-0 ns-aoiok tidb-hdfezd tidb-pd Running leader us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-12-152.us-west-2.compute.internal/172.31.12.152 May 28,2025 11:54 UTC+0800 tidb-hdfezd-tikv-0 ns-aoiok tidb-hdfezd tikv Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-11-7.us-west-2.compute.internal/172.31.11.7 May 28,2025 11:54 UTC+0800 tidb-hdfezd-tikv-1 ns-aoiok tidb-hdfezd tikv Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-13-212.us-west-2.compute.internal/172.31.13.212 May 28,2025 11:53 UTC+0800 check pod status done connect unsupported engine type: tidb tidb-7-1.0.0-alpha.0 check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-restart-xwk9l ns-aoiok Restart tidb-hdfezd tidb-pd,tikv,tidb Succeed 5/5 May 28,2025 11:52 UTC+0800 check ops status done ops_status:tidb-hdfezd-restart-xwk9l ns-aoiok Restart tidb-hdfezd tidb-pd,tikv,tidb Succeed 5/5 May 28,2025 11:52 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations tidb-hdfezd-restart-xwk9l --namespace ns-aoiok ` opsrequest.operations.kubeblocks.io/tidb-hdfezd-restart-xwk9l patched `kbcli cluster delete-ops --name tidb-hdfezd-restart-xwk9l --force --auto-approve --namespace ns-aoiok ` OpsRequest tidb-hdfezd-restart-xwk9l deleted cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop tidb-hdfezd --auto-approve --force=true --namespace ns-aoiok ` OpsRequest tidb-hdfezd-stop-m6mqz created successfully, you can view the progress: kbcli cluster describe-ops tidb-hdfezd-stop-m6mqz -n ns-aoiok check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-stop-m6mqz ns-aoiok Stop tidb-hdfezd tidb,tidb-pd,tikv Running 0/5 May 28,2025 11:55 UTC+0800 check cluster status `kbcli cluster list tidb-hdfezd --show-labels --namespace ns-aoiok ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS tidb-hdfezd ns-aoiok tidb DoNotTerminate Stopping May 28,2025 11:38 UTC+0800 app.kubernetes.io/instance=tidb-hdfezd,clusterdefinition.kubeblocks.io/name=tidb cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping check cluster status done cluster_status:Stopped check pod status `kbcli cluster list-instances tidb-hdfezd --namespace ns-aoiok ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME check pod status done check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-stop-m6mqz ns-aoiok Stop tidb-hdfezd tidb,tidb-pd,tikv Succeed 5/5 May 28,2025 11:55 UTC+0800 check ops status done ops_status:tidb-hdfezd-stop-m6mqz ns-aoiok Stop tidb-hdfezd tidb,tidb-pd,tikv Succeed 5/5 May 28,2025 11:55 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations tidb-hdfezd-stop-m6mqz --namespace ns-aoiok ` opsrequest.operations.kubeblocks.io/tidb-hdfezd-stop-m6mqz patched `kbcli cluster delete-ops --name tidb-hdfezd-stop-m6mqz --force --auto-approve --namespace ns-aoiok ` OpsRequest tidb-hdfezd-stop-m6mqz deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start tidb-hdfezd --force=true --namespace ns-aoiok ` OpsRequest tidb-hdfezd-start-rmxs8 created successfully, you can view the progress: kbcli cluster describe-ops tidb-hdfezd-start-rmxs8 -n ns-aoiok check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-start-rmxs8 ns-aoiok Start tidb-hdfezd tidb,tidb-pd,tikv Running 0/5 May 28,2025 11:57 UTC+0800 check cluster status `kbcli cluster list tidb-hdfezd --show-labels --namespace ns-aoiok ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS tidb-hdfezd ns-aoiok tidb DoNotTerminate Updating May 28,2025 11:38 UTC+0800 app.kubernetes.io/instance=tidb-hdfezd,clusterdefinition.kubeblocks.io/name=tidb cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances tidb-hdfezd --namespace ns-aoiok ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME tidb-hdfezd-tidb-0 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-12-133.us-west-2.compute.internal/172.31.12.133 May 28,2025 11:57 UTC+0800 tidb-hdfezd-tidb-1 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-7-74.us-west-2.compute.internal/172.31.7.74 May 28,2025 11:57 UTC+0800 tidb-hdfezd-tidb-pd-0 ns-aoiok tidb-hdfezd tidb-pd Running leader us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-12-152.us-west-2.compute.internal/172.31.12.152 May 28,2025 11:58 UTC+0800 tidb-hdfezd-tikv-0 ns-aoiok tidb-hdfezd tikv Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-13-212.us-west-2.compute.internal/172.31.13.212 May 28,2025 11:57 UTC+0800 tidb-hdfezd-tikv-1 ns-aoiok tidb-hdfezd tikv Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-11-7.us-west-2.compute.internal/172.31.11.7 May 28,2025 11:57 UTC+0800 check pod status done connect unsupported engine type: tidb tidb-7-1.0.0-alpha.0 check ops status `kbcli cluster list-ops tidb-hdfezd --status all --namespace ns-aoiok ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME tidb-hdfezd-start-rmxs8 ns-aoiok Start tidb-hdfezd tidb,tidb-pd,tikv Succeed 5/5 May 28,2025 11:57 UTC+0800 check ops status done ops_status:tidb-hdfezd-start-rmxs8 ns-aoiok Start tidb-hdfezd tidb,tidb-pd,tikv Succeed 5/5 May 28,2025 11:57 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations tidb-hdfezd-start-rmxs8 --namespace ns-aoiok ` opsrequest.operations.kubeblocks.io/tidb-hdfezd-start-rmxs8 patched `kbcli cluster delete-ops --name tidb-hdfezd-start-rmxs8 --force --auto-approve --namespace ns-aoiok ` OpsRequest tidb-hdfezd-start-rmxs8 deleted cluster update terminationPolicy WipeOut `kbcli cluster update tidb-hdfezd --termination-policy=WipeOut --namespace ns-aoiok ` cluster.apps.kubeblocks.io/tidb-hdfezd updated check cluster status `kbcli cluster list tidb-hdfezd --show-labels --namespace ns-aoiok ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS tidb-hdfezd ns-aoiok tidb WipeOut Running May 28,2025 11:38 UTC+0800 app.kubernetes.io/instance=tidb-hdfezd,clusterdefinition.kubeblocks.io/name=tidb check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances tidb-hdfezd --namespace ns-aoiok ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME tidb-hdfezd-tidb-0 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-12-133.us-west-2.compute.internal/172.31.12.133 May 28,2025 11:57 UTC+0800 tidb-hdfezd-tidb-1 ns-aoiok tidb-hdfezd tidb Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m ip-172-31-7-74.us-west-2.compute.internal/172.31.7.74 May 28,2025 11:57 UTC+0800 tidb-hdfezd-tidb-pd-0 ns-aoiok tidb-hdfezd tidb-pd Running leader us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-12-152.us-west-2.compute.internal/172.31.12.152 May 28,2025 11:58 UTC+0800 tidb-hdfezd-tikv-0 ns-aoiok tidb-hdfezd tikv Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-13-212.us-west-2.compute.internal/172.31.13.212 May 28,2025 11:57 UTC+0800 tidb-hdfezd-tikv-1 ns-aoiok tidb-hdfezd tikv Running us-west-2a 600m / 600m 3328599654400m / 3328599654400m data:22Gi ip-172-31-11-7.us-west-2.compute.internal/172.31.11.7 May 28,2025 11:57 UTC+0800 check pod status done connect unsupported engine type: tidb tidb-7-1.0.0-alpha.0 cluster list-logs `kbcli cluster list-logs tidb-hdfezd --namespace ns-aoiok ` No log files found. Error from server (NotFound): pods "tidb-hdfezd-tidb-0" not found cluster logs `kbcli cluster logs tidb-hdfezd --tail 30 --namespace ns-aoiok ` Defaulted container "pd" out of: pd, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), init-pd-ctl (init) [2025/05/28 03:58:37.635 +00:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=tidb-hdfezd-tidb-0.tidb-hdfezd-tidb-headless.ns-aoiok.svc.cluster.local:4000] [interval=2s] [error="dial tcp 172.31.12.73:4000: connect: connection refused"] [2025/05/28 03:58:37.635 +00:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=tidb-hdfezd-tidb-0.tidb-hdfezd-tidb-headless.ns-aoiok.svc.cluster.local:10080] [interval=2s] [error="dial tcp 172.31.12.73:10080: connect: connection refused"] [2025/05/28 03:58:39.635 +00:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=tidb-hdfezd-tidb-0.tidb-hdfezd-tidb-headless.ns-aoiok.svc.cluster.local:10080] [interval=2s] [error="dial tcp 172.31.12.73:10080: connect: connection refused"] [2025/05/28 03:58:39.635 +00:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=tidb-hdfezd-tidb-0.tidb-hdfezd-tidb-headless.ns-aoiok.svc.cluster.local:4000] [interval=2s] [error="dial tcp 172.31.12.73:4000: connect: connection refused"] [2025/05/28 03:58:40.636 +00:00] [WARN] [tidb.go:65] ["Alive of TiDB has expired, maybe local time in different hosts are not synchronized"] [key=/topology/tidb/tidb-hdfezd-tidb-0.tidb-hdfezd-tidb-headless.ns-aoiok.svc.cluster.local:4000/ttl] [value=1748404565810509081] [2025/05/28 03:58:41.636 +00:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=tidb-hdfezd-tidb-0.tidb-hdfezd-tidb-headless.ns-aoiok.svc.cluster.local:4000] [interval=2s] [error="dial tcp 172.31.12.73:4000: connect: connection refused"] [2025/05/28 03:58:41.636 +00:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=tidb-hdfezd-tidb-0.tidb-hdfezd-tidb-headless.ns-aoiok.svc.cluster.local:10080] [interval=2s] [error="dial tcp 172.31.12.73:10080: connect: connection refused"] [2025/05/28 03:58:43.637 +00:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=tidb-hdfezd-tidb-0.tidb-hdfezd-tidb-headless.ns-aoiok.svc.cluster.local:10080] [interval=2s] [error="dial tcp 172.31.12.73:10080: connect: connection refused"] [2025/05/28 03:58:43.637 +00:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=tidb-hdfezd-tidb-0.tidb-hdfezd-tidb-headless.ns-aoiok.svc.cluster.local:4000] [interval=2s] [error="dial tcp 172.31.12.73:4000: connect: connection refused"] [2025/05/28 03:58:45.637 +00:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=tidb-hdfezd-tidb-0.tidb-hdfezd-tidb-headless.ns-aoiok.svc.cluster.local:10080] [interval=2s] [error="dial tcp 172.31.12.73:10080: connect: connection refused"] [2025/05/28 03:58:45.637 +00:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=tidb-hdfezd-tidb-0.tidb-hdfezd-tidb-headless.ns-aoiok.svc.cluster.local:4000] [interval=2s] [error="dial tcp 172.31.12.73:4000: connect: connection refused"] [2025/05/28 03:58:45.638 +00:00] [WARN] [tidb.go:65] ["Alive of TiDB has expired, maybe local time in different hosts are not synchronized"] [key=/topology/tidb/tidb-hdfezd-tidb-0.tidb-hdfezd-tidb-headless.ns-aoiok.svc.cluster.local:4000/ttl] [value=1748404565810509081] [2025/05/28 03:58:48.209 +00:00] [INFO] [prepare_checker.go:65] ["not loaded from storage region number is satisfied, finish prepare checker"] [not-from-storage-region=52] [total-region=53] [2025/05/28 03:58:48.209 +00:00] [INFO] [coordinator.go:344] ["coordinator has finished cluster information preparation"] [2025/05/28 03:58:48.209 +00:00] [INFO] [coordinator.go:354] ["coordinator starts to run schedulers"] [2025/05/28 03:58:48.210 +00:00] [INFO] [coordinator.go:402] ["create scheduler with independent configuration"] [scheduler-name=balance-hot-region-scheduler] [2025/05/28 03:58:48.212 +00:00] [INFO] [coordinator.go:402] ["create scheduler with independent configuration"] [scheduler-name=balance-leader-scheduler] [2025/05/28 03:58:48.214 +00:00] [INFO] [coordinator.go:402] ["create scheduler with independent configuration"] [scheduler-name=balance-region-scheduler] [2025/05/28 03:58:48.215 +00:00] [INFO] [coordinator.go:402] ["create scheduler with independent configuration"] [scheduler-name=balance-witness-scheduler] [2025/05/28 03:58:48.217 +00:00] [INFO] [coordinator.go:402] ["create scheduler with independent configuration"] [scheduler-name=transfer-witness-leader-scheduler] [2025/05/28 03:58:48.219 +00:00] [INFO] [coordinator.go:424] ["create scheduler"] [scheduler-name=balance-region-scheduler] [scheduler-args="[]"] [2025/05/28 03:58:48.219 +00:00] [INFO] [coordinator.go:424] ["create scheduler"] [scheduler-name=balance-leader-scheduler] [scheduler-args="[]"] [2025/05/28 03:58:48.219 +00:00] [INFO] [coordinator.go:424] ["create scheduler"] [scheduler-name=balance-witness-scheduler] [scheduler-args="[]"] [2025/05/28 03:58:48.219 +00:00] [INFO] [coordinator.go:424] ["create scheduler"] [scheduler-name=balance-hot-region-scheduler] [scheduler-args="[]"] [2025/05/28 03:58:48.219 +00:00] [INFO] [coordinator.go:424] ["create scheduler"] [scheduler-name=transfer-witness-leader-scheduler] [scheduler-args="[]"] [2025/05/28 03:58:48.222 +00:00] [INFO] [coordinator.go:313] ["coordinator begins to actively drive push operator"] [2025/05/28 03:58:48.222 +00:00] [INFO] [coordinator.go:142] ["coordinator starts patrol regions"] [2025/05/28 03:58:48.222 +00:00] [INFO] [coordinator.go:249] ["coordinator begins to check suspect key ranges"] [2025/05/28 03:58:49.210 +00:00] [INFO] [hot_region_config.go:441] ["query supported changed"] [last-query-support=false] [cluster-version=7.1.5] [config="***\"min-hot-byte-rate\":100,\"min-hot-key-rate\":10,\"min-hot-query-rate\":10,\"max-zombie-rounds\":3,\"max-peer-number\":1000,\"byte-rate-rank-step-ratio\":0.05,\"key-rate-rank-step-ratio\":0.05,\"query-rate-rank-step-ratio\":0.05,\"count-rank-step-ratio\":0.01,\"great-dec-ratio\":0.95,\"minor-dec-ratio\":0.99,\"src-tolerance-ratio\":1.05,\"dst-tolerance-ratio\":1.05,\"write-leader-priorities\":[\"query\",\"byte\"],\"write-peer-priorities\":[\"byte\",\"key\"],\"read-priorities\":[\"query\",\"byte\"],\"strict-picking-store\":\"true\",\"enable-for-tiflash\":\"true\",\"rank-formula-version\":\"v2\",\"forbid-rw-type\":\"none\"***"] [valid-config="***\"min-hot-byte-rate\":100,\"min-hot-key-rate\":10,\"min-hot-query-rate\":10,\"max-zombie-rounds\":3,\"max-peer-number\":1000,\"byte-rate-rank-step-ratio\":0.05,\"key-rate-rank-step-ratio\":0.05,\"query-rate-rank-step-ratio\":0.05,\"count-rank-step-ratio\":0.01,\"great-dec-ratio\":0.95,\"minor-dec-ratio\":0.99,\"src-tolerance-ratio\":1.05,\"dst-tolerance-ratio\":1.05,\"write-leader-priorities\":[\"key\",\"byte\"],\"write-peer-priorities\":[\"byte\",\"key\"],\"read-priorities\":[\"byte\",\"key\"],\"strict-picking-store\":\"true\",\"enable-for-tiflash\":\"true\",\"rank-formula-version\":\"v2\"***"] [2025/05/28 03:59:24.214 +00:00] [INFO] [store_config.go:234] ["sync the store config successful"] [store-address=172.31.5.28:20180] [store-config="***\n \"coprocessor\": ***\n \"region-max-size\": \"144MiB\",\n \"region-split-size\": \"96MiB\",\n \"region-max-keys\": 1440000,\n \"region-split-keys\": 960000,\n \"enable-region-bucket\": false,\n \"region-bucket-size\": \"96MiB\"\n ***,\n \"storage\": ***\n \"engine\": \"raft-kv\"\n ***\n***"] [old-config="***\n \"coprocessor\": ***\n \"region-max-size\": \"\",\n \"region-split-size\": \"\",\n \"region-max-keys\": 0,\n \"region-split-keys\": 0,\n \"enable-region-bucket\": false,\n \"region-bucket-size\": \"\"\n ***,\n \"storage\": ***\n \"engine\": \"\"\n ***\n***"] delete cluster tidb-hdfezd `kbcli cluster delete tidb-hdfezd --auto-approve --namespace ns-aoiok ` Cluster tidb-hdfezd deleted pod_info:tidb-hdfezd-tidb-0 3/3 Terminating 1 (64s ago) 2m47s tidb-hdfezd-tidb-1 3/3 Terminating 0 2m36s tidb-hdfezd-tidb-pd-0 3/3 Running 0 100s tidb-hdfezd-tikv-0 2/2 Running 0 2m14s tidb-hdfezd-tikv-1 2/2 Running 0 117s pod_info:tidb-hdfezd-tidb-0 3/3 Terminating 1 (85s ago) 3m8s tidb-hdfezd-tidb-1 3/3 Terminating 0 2m57s tidb-hdfezd-tidb-pd-0 3/3 Running 0 2m1s tidb-hdfezd-tikv-0 2/2 Running 0 2m35s tidb-hdfezd-tikv-1 2/2 Running 0 2m18s No resources found in ns-aoiok namespace. delete cluster pod done No resources found in ns-aoiok namespace. check cluster resource non-exist OK: pvc No resources found in ns-aoiok namespace. delete cluster done No resources found in ns-aoiok namespace. No resources found in ns-aoiok namespace. No resources found in ns-aoiok namespace. Tidb Test Suite All Done! --------------------------------------Tidb (Topology = cluster Replicas 2) Test Result-------------------------------------- [PASSED]|[Create]|[ComponentDefinition=tidb-7-1.0.0-alpha.0;ComponentVersion=tidb;ServiceVersion=7.1.5;]|[Description=Create a cluster with the specified component definition tidb-7-1.0.0-alpha.0 and component version tidb and service version 7.1.5] [PASSED]|[Connect]|[ComponentName=tidb]|[Description=Connect to the cluster] [PASSED]|[VerticalScaling]|[ComponentName=tidb]|[Description=VerticalScaling the cluster specify component tidb] [PASSED]|[Restart]|[ComponentName=tidb,tikv]|[Description=Restart the cluster specify component tidb,tikv] [PASSED]|[VolumeExpansion]|[ComponentName=tidb-pd,tikv]|[Description=VolumeExpansion the cluster specify component tidb-pd,tikv] [PASSED]|[HorizontalScaling Out]|[ComponentName=tidb]|[Description=HorizontalScaling Out the cluster specify component tidb] [PASSED]|[HorizontalScaling In]|[ComponentName=tidb]|[Description=HorizontalScaling In the cluster specify component tidb] [PASSED]|[VerticalScaling]|[ComponentName=tidb-pd,tikv]|[Description=VerticalScaling the cluster specify component tidb-pd,tikv] [PASSED]|[HorizontalScaling Out]|[ComponentName=tikv]|[Description=HorizontalScaling Out the cluster specify component tikv] [PASSED]|[Restart]|[-]|[Description=Restart the cluster] [PASSED]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut] [PASSED]|[Delete]|[-]|[Description=Delete the cluster] [END]