source commons files source engines files source kubeblocks files `kubectl get namespace | grep ns-riept ` `kubectl create namespace ns-riept` namespace/ns-riept created create namespace ns-riept done download kbcli `gh release list --repo apecloud/kbcli --limit 100 | (grep "0.9" || true)` `curl -fsSL https://kubeblocks.io/installer/install_cli.sh | bash -s v0.9.4-beta.1` 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 32.1M 100 32.1M 0 0 103M 0 --:--:-- --:--:-- --:--:-- 103M kbcli installed successfully. Kubernetes: v1.32.5-eks-5d4a308 KubeBlocks: 0.9.4 kbcli: 0.9.4-beta.1 WARNING: version difference between kbcli (0.9.4-beta.1) and kubeblocks (0.9.4) 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 v0.9.4-beta.1 done Kubernetes: v1.32.5-eks-5d4a308 KubeBlocks: 0.9.4 kbcli: 0.9.4-beta.1 WARNING: version difference between kbcli (0.9.4-beta.1) and kubeblocks (0.9.4) Kubernetes Env: v1.32.5-eks-5d4a308 POD_RESOURCES: No resources found found default storage class: gp3 kubeblocks version is:0.9.4 skip upgrade kubeblocks 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 cluster definition set component name:fe set component version set component version:starrocks-be set service versions:3.2.2,3.3.0,3.3.2,3.3.3,3.4.1 set service versions sorted:3.2.2,3.3.0,3.3.2,3.3.3,3.4.1 no cluster version found set replicas first:2,3.2.2|2,3.3.0|2,3.3.2|2,3.3.3|2,3.4.1 set replicas third:2,3.2.2 set replicas fourth:2,3.2.2 set minimum cmpv service version set minimum cmpv service version replicas:2,3.2.2 REPORT_COUNT:1 CLUSTER_TOPOLOGY:shared-data topology shared-data found in cluster definition starrocks LIMIT_CPU:1 LIMIT_MEMORY:2 storage size: 20 No resources found in ns-riept namespace. termination_policy:DoNotTerminate create 2 replica DoNotTerminate starrocks cluster check cluster definition check component definition set component definition by component version check cmpd by labels set component definition2: starrocks-be by component version:starrocks-be apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: strent-hzrqlx namespace: ns-riept spec: clusterDefinitionRef: starrocks topology: shared-data terminationPolicy: DoNotTerminate componentSpecs: - name: cn serviceVersion: 3.2.2 serviceAccountName: kb-strent-hzrqlx replicas: 2 resources: requests: cpu: 1000m memory: 2Gi limits: cpu: 1000m memory: 2Gi - name: fe serviceVersion: 3.2.2 serviceAccountName: kb-strent-hzrqlx replicas: 3 resources: requests: cpu: 1000m memory: 2Gi limits: cpu: 1000m memory: 2Gi volumeClaimTemplates: - name: data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi `kubectl apply -f test_create_strent-hzrqlx.yaml` cluster.apps.kubeblocks.io/strent-hzrqlx created apply test_create_strent-hzrqlx.yaml Success `rm -rf test_create_strent-hzrqlx.yaml` check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Jun 19,2025 18:13 UTC+0800 clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= cluster_status: cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating 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 strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1 / 1 2Gi / 2Gi ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:15 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1 / 1 2Gi / 2Gi ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:15 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-1-25.us-west-2.compute.internal/172.31.1.25 Jun 19,2025 18:13 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:13 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:13 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check pod strent-hzrqlx-cn-0 container_name cn exist password pir8D7Z845 check pod strent-hzrqlx-cn-0 container_name nginx exist password pir8D7Z845 check pod strent-hzrqlx-cn-0 container_name lorry exist password pir8D7Z845 check pod strent-hzrqlx-cn-0 container_name config-manager exist password pir8D7Z845 No container logs contain secret password. describe cluster `kbcli cluster describe strent-hzrqlx --namespace ns-riept ` Name: strent-hzrqlx Created Time: Jun 19,2025 18:13 UTC+0800 NAMESPACE CLUSTER-DEFINITION VERSION STATUS TERMINATION-POLICY ns-riept starrocks Running DoNotTerminate Endpoints: COMPONENT MODE INTERNAL EXTERNAL fe ReadWrite strent-hzrqlx-fe-fe.ns-riept.svc.cluster.local:8030 strent-hzrqlx-fe-fe.ns-riept.svc.cluster.local:9030 cn ReadWrite strent-hzrqlx-cn-cn.ns-riept.svc.cluster.local:8040 strent-hzrqlx-cn-cn.ns-riept.svc.cluster.local:8080 Topology: COMPONENT INSTANCE ROLE STATUS AZ NODE CREATED-TIME cn strent-hzrqlx-cn-0 Running us-west-2a ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:15 UTC+0800 cn strent-hzrqlx-cn-1 Running us-west-2a ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:15 UTC+0800 fe strent-hzrqlx-fe-0 Running us-west-2a ip-172-31-1-25.us-west-2.compute.internal/172.31.1.25 Jun 19,2025 18:13 UTC+0800 fe strent-hzrqlx-fe-1 Running us-west-2a ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:13 UTC+0800 fe strent-hzrqlx-fe-2 Running us-west-2a ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:13 UTC+0800 Resources Allocation: COMPONENT DEDICATED CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS fe false 1 / 1 2Gi / 2Gi data:20Gi kb-default-sc cn false 1 / 1 2Gi / 2Gi Images: COMPONENT TYPE IMAGE fe docker.io/apecloud/fe-ubuntu:3.2.2 cn docker.io/apecloud/cn-ubuntu:3.2.2 Show cluster events: kbcli cluster list-events -n ns-riept strent-hzrqlx `kbcli cluster label strent-hzrqlx app.kubernetes.io/instance- --namespace ns-riept ` label "app.kubernetes.io/instance" not found. `kbcli cluster label strent-hzrqlx app.kubernetes.io/instance=strent-hzrqlx --namespace ns-riept ` `kbcli cluster label strent-hzrqlx --list --namespace ns-riept ` NAME NAMESPACE LABELS strent-hzrqlx ns-riept app.kubernetes.io/instance=strent-hzrqlx clusterdefinition.kubeblocks.io/name=starrocks clusterversion.kubeblocks.io/name= label cluster app.kubernetes.io/instance=strent-hzrqlx Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=strent-hzrqlx --namespace ns-riept ` `kbcli cluster label strent-hzrqlx --list --namespace ns-riept ` NAME NAMESPACE LABELS strent-hzrqlx ns-riept app.kubernetes.io/instance=strent-hzrqlx case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=starrocks clusterversion.kubeblocks.io/name= label cluster case.name=kbcli.test1 Success `kbcli cluster label strent-hzrqlx case.name=kbcli.test2 --overwrite --namespace ns-riept ` `kbcli cluster label strent-hzrqlx --list --namespace ns-riept ` NAME NAMESPACE LABELS strent-hzrqlx ns-riept app.kubernetes.io/instance=strent-hzrqlx case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=starrocks clusterversion.kubeblocks.io/name= label cluster case.name=kbcli.test2 Success `kbcli cluster label strent-hzrqlx case.name- --namespace ns-riept ` `kbcli cluster label strent-hzrqlx --list --namespace ns-riept ` NAME NAMESPACE LABELS strent-hzrqlx ns-riept app.kubernetes.io/instance=strent-hzrqlx clusterdefinition.kubeblocks.io/name=starrocks clusterversion.kubeblocks.io/name= delete cluster label case.name Success cluster connect `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys KUBEBLOCKS NAMESPACE:kb-zkhtd get kubeblocks namespace done `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-zkhtd -o jsonpath="***.items[0].data.root-user***"` `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-zkhtd -o jsonpath="***.items[0].data.root-password***"` minio_user:kbclitest,minio_password:kbclitest,minio_endpoint:kbcli-test-minio.kb-zkhtd.svc.cluster.local:9000 list minio bucket kbcli-test `echo 'mc config host add minioserver http://kbcli-test-minio.kb-zkhtd.svc.cluster.local:9000 kbclitest kbclitest;mc ls minioserver' | kubectl exec -it kbcli-test-minio-d9bd755d8-fxn5w --namespace kb-zkhtd -- bash` Unable to use a TTY - input is not a terminal or the right kind of file list minio bucket done `echo "echo \" CREATE STORAGE VOLUME sr_djrha TYPE = S3 LOCATIONS = ('s3://kbcli-test/') PROPERTIES ( 'enabled' = 'true', 'aws.s3.endpoint' = 'http://kbcli-test-minio.kb-zkhtd.svc.cluster.local:9000', 'aws.s3.access_key' = 'kbclitest', 'aws.s3.secret_key' = 'kbclitest' ); SET sr_djrha AS DEFAULT STORAGE VOLUME; \" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash ` Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. connect cluster Success insert batch data by db client Error from server (NotFound): pods "test-db-client-executionloop-strent-hzrqlx" not found DB_CLIENT_BATCH_DATA_COUNT: `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-executionloop-strent-hzrqlx --namespace ns-riept ` Error from server (NotFound): pods "test-db-client-executionloop-strent-hzrqlx" not found 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. Error from server (NotFound): pods "test-db-client-executionloop-strent-hzrqlx" not found `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys apiVersion: v1 kind: Pod metadata: name: test-db-client-executionloop-strent-hzrqlx namespace: ns-riept spec: containers: - name: test-dbclient imagePullPolicy: IfNotPresent image: docker.io/apecloud/dbclient:test args: - "--host" - "strent-hzrqlx-fe-fe.ns-riept.svc.cluster.local" - "--user" - "root" - "--password" - "pir8D7Z845" - "--port" - "9030" - "--dbtype" - "starrocks" - "--test" - "executionloop" - "--duration" - "60" - "--interval" - "1" restartPolicy: Never `kubectl apply -f test-db-client-executionloop-strent-hzrqlx.yaml` pod/test-db-client-executionloop-strent-hzrqlx created apply test-db-client-executionloop-strent-hzrqlx.yaml Success `rm -rf test-db-client-executionloop-strent-hzrqlx.yaml` check pod status pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 0/1 ContainerCreating 0 6s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 1/1 Running 0 11s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 1/1 Running 0 17s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 1/1 Running 0 23s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 1/1 Running 0 29s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 1/1 Running 0 36s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 1/1 Running 0 42s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 1/1 Running 0 48s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 1/1 Running 0 54s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 1/1 Running 0 60s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 1/1 Running 0 66s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 1/1 Running 0 72s check pod test-db-client-executionloop-strent-hzrqlx status done pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-hzrqlx 0/1 Completed 0 78s check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Running Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1 / 1 2Gi / 2Gi ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:15 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1 / 1 2Gi / 2Gi ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:15 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-1-25.us-west-2.compute.internal/172.31.1.25 Jun 19,2025 18:13 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:13 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:13 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done --host strent-hzrqlx-fe-fe.ns-riept.svc.cluster.local --user root --password pir8D7Z845 --port 9030 --dbtype starrocks --test executionloop --duration 60 --interval 1 SLF4J(I): Connected with provider of type [ch.qos.logback.classic.spi.LogbackServiceProvider] 10:18:33.190 [main] DEBUG com.clickhouse.jdbc.ClickHouseDriver -- ClickHouse Driver 0.0.0.0(JDBC: 0.0.0.0) registered Execution loop start: create databases executions_loop CREATE DATABASE IF NOT EXISTS executions_loop; drop table executions_loop_table DROP TABLE IF EXISTS executions_loop.executions_loop_table; create table executions_loop_table CREATE TABLE IF NOT EXISTS executions_loop.executions_loop_table (id INT, value VARCHAR(255), tinyint_col TINYINT, smallint_col SMALLINT, int_col INT, bigint_col BIGINT, float_col FLOAT, double_col DOUBLE, decimal_col DECIMAL(10, 2), date_col DATE, datetime_col DATETIME, char_col CHAR(10), text_col TEXT, binary_col BINARY(30), varbinary_col VARBINARY(255), enum_col VARCHAR(20), set_col VARCHAR(50) ) ENGINE=OLAP DUPLICATE KEY(id) DISTRIBUTED BY HASH(id) BUCKETS 3 PROPERTIES ( 'replication_num' = '1' ); Execution loop start:INSERT INTO executions_loop.executions_loop_table (value, tinyint_col, smallint_col, int_col, bigint_col, float_col, double_col, decimal_col, date_col, datetime_col, char_col, text_col, binary_col, varbinary_col, enum_col, set_col) VALUES ('executions_loop_test_1', 105, 11058, 1751457147, 5372458396329050599, 0.2558956, 0.583625396413807, 85.05637701973194, '2025-06-19', '2025-06-19 10:18:34.276', 'PprCq1QWgi', 'iBGCrUfeNVrLze2DLvR4igWW8n59inx4afl4lS5hsSodYJFHgYEX1YUhBT3cHhKqybXpFFKRL2rSE1WwqXAPxHYJOBVCwJvLqCp1OZGJtaj62cY1q5c6Xsk6NOv5SHgyBUWMMRL3pAB1I6Wl9UEkdrm3QvW9hLtHSldOnJDTJ5YyUqExVHLB3yH2bG2jr62PLkl9NJEzDEKjrCpKsTYiRxpUd82ZkrAmZmtcPUgXvFJJWU0Gx4u5xkFktW91uK1', TO_BINARY('base64,XfCwzoawKLTMaw=='), TO_BINARY('base64,gX0WPzI1ylyHk/0BOJ3xTv/Pl4ZdQMlK/zGoJAqlY0sb5FyQhf+Qr5tZE2Xl9WlBGVL4Umhu/Rjaobm84bwlemC6EAYfeJrZAm6W3W7u0mmTGs4ZpigRY1ea0OpxvQBs4d8eI5zyd6uKSEYDs+C3bZxKi2BGDTvLcH+kZXtK9dYI96Ln2S4eufORLLl4NiZidZ95X/gmKQpNgfQ='), 'Option1', 'Value1' ); [ 1s ] executions total: 1 successful: 1 failed: 0 disconnect: 0 [ 2s ] executions total: 6 successful: 6 failed: 0 disconnect: 0 [ 3s ] executions total: 11 successful: 11 failed: 0 disconnect: 0 [ 4s ] executions total: 19 successful: 19 failed: 0 disconnect: 0 [ 5s ] executions total: 28 successful: 28 failed: 0 disconnect: 0 [ 6s ] executions total: 38 successful: 38 failed: 0 disconnect: 0 [ 7s ] executions total: 50 successful: 50 failed: 0 disconnect: 0 [ 8s ] executions total: 62 successful: 62 failed: 0 disconnect: 0 [ 9s ] executions total: 74 successful: 74 failed: 0 disconnect: 0 [ 10s ] executions total: 83 successful: 83 failed: 0 disconnect: 0 [ 11s ] executions total: 93 successful: 93 failed: 0 disconnect: 0 [ 12s ] executions total: 104 successful: 104 failed: 0 disconnect: 0 [ 13s ] executions total: 113 successful: 113 failed: 0 disconnect: 0 [ 14s ] executions total: 122 successful: 122 failed: 0 disconnect: 0 [ 15s ] executions total: 133 successful: 133 failed: 0 disconnect: 0 [ 16s ] executions total: 136 successful: 136 failed: 0 disconnect: 0 [ 17s ] executions total: 147 successful: 147 failed: 0 disconnect: 0 [ 18s ] executions total: 150 successful: 150 failed: 0 disconnect: 0 [ 19s ] executions total: 151 successful: 151 failed: 0 disconnect: 0 [ 20s ] executions total: 162 successful: 162 failed: 0 disconnect: 0 [ 21s ] executions total: 174 successful: 174 failed: 0 disconnect: 0 [ 22s ] executions total: 187 successful: 187 failed: 0 disconnect: 0 [ 23s ] executions total: 198 successful: 198 failed: 0 disconnect: 0 [ 24s ] executions total: 210 successful: 210 failed: 0 disconnect: 0 [ 25s ] executions total: 222 successful: 222 failed: 0 disconnect: 0 [ 26s ] executions total: 234 successful: 234 failed: 0 disconnect: 0 [ 27s ] executions total: 246 successful: 246 failed: 0 disconnect: 0 [ 28s ] executions total: 252 successful: 252 failed: 0 disconnect: 0 [ 29s ] executions total: 264 successful: 264 failed: 0 disconnect: 0 [ 30s ] executions total: 276 successful: 276 failed: 0 disconnect: 0 [ 31s ] executions total: 289 successful: 289 failed: 0 disconnect: 0 [ 32s ] executions total: 301 successful: 301 failed: 0 disconnect: 0 [ 33s ] executions total: 313 successful: 313 failed: 0 disconnect: 0 [ 34s ] executions total: 325 successful: 325 failed: 0 disconnect: 0 [ 35s ] executions total: 337 successful: 337 failed: 0 disconnect: 0 [ 36s ] executions total: 350 successful: 350 failed: 0 disconnect: 0 [ 37s ] executions total: 360 successful: 360 failed: 0 disconnect: 0 [ 38s ] executions total: 372 successful: 372 failed: 0 disconnect: 0 [ 39s ] executions total: 385 successful: 385 failed: 0 disconnect: 0 [ 40s ] executions total: 395 successful: 395 failed: 0 disconnect: 0 [ 41s ] executions total: 408 successful: 408 failed: 0 disconnect: 0 [ 42s ] executions total: 420 successful: 420 failed: 0 disconnect: 0 [ 60s ] executions total: 430 successful: 430 failed: 0 disconnect: 0 Test Result: Total Executions: 430 Successful Executions: 430 Failed Executions: 0 Disconnection Counts: 0 Connection Information: Database Type: starrocks Host: strent-hzrqlx-fe-fe.ns-riept.svc.cluster.local Port: 9030 Database: Table: User: root Org: Access Mode: mysql Test Type: executionloop Query: Duration: 60 seconds Interval: 1 seconds DB_CLIENT_BATCH_DATA_COUNT: 430 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-executionloop-strent-hzrqlx --namespace ns-riept ` pod/test-db-client-executionloop-strent-hzrqlx patched (no change) 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 "test-db-client-executionloop-strent-hzrqlx" force deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo \"CREATE DATABASE IF NOT EXISTS mydb; use mydb; DROP TABLE IF EXISTS tmp_table; CREATE TABLE IF NOT EXISTS tmp_table (id INT, value STRING) ; INSERT INTO tmp_table (id, value) VALUES (1,'qmhav');\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. add consistent data qmhav Success cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose strent-hzrqlx --auto-approve --force=true --type internet --enable true --components fe --namespace ns-riept ` OpsRequest strent-hzrqlx-expose-bckcv created successfully, you can view the progress: kbcli cluster describe-ops strent-hzrqlx-expose-bckcv -n ns-riept check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-expose-bckcv ns-riept Expose strent-hzrqlx Creating -/- Jun 19,2025 18:20 UTC+0800 check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Running Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1 / 1 2Gi / 2Gi ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:15 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1 / 1 2Gi / 2Gi ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:15 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-1-25.us-west-2.compute.internal/172.31.1.25 Jun 19,2025 18:13 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:13 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:13 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-expose-bckcv ns-riept Expose strent-hzrqlx fe Succeed 1/1 Jun 19,2025 18:20 UTC+0800 check ops status done ops_status:strent-hzrqlx-expose-bckcv ns-riept Expose strent-hzrqlx fe Succeed 1/1 Jun 19,2025 18:20 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-hzrqlx-expose-bckcv --namespace ns-riept ` opsrequest.apps.kubeblocks.io/strent-hzrqlx-expose-bckcv patched `kbcli cluster delete-ops --name strent-hzrqlx-expose-bckcv --force --auto-approve --namespace ns-riept ` OpsRequest strent-hzrqlx-expose-bckcv deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value qmhav check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -- bash ` check db_client batch data Success cluster vscale check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale strent-hzrqlx --auto-approve --force=true --components cn --cpu 1100m --memory 2.1Gi --namespace ns-riept ` OpsRequest strent-hzrqlx-verticalscaling-k9vfc created successfully, you can view the progress: kbcli cluster describe-ops strent-hzrqlx-verticalscaling-k9vfc -n ns-riept check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-verticalscaling-k9vfc ns-riept VerticalScaling strent-hzrqlx cn Running -/- Jun 19,2025 18:21 UTC+0800 check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Updating Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= 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 strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:21 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:21 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-1-25.us-west-2.compute.internal/172.31.1.25 Jun 19,2025 18:13 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:13 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:13 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-verticalscaling-k9vfc ns-riept VerticalScaling strent-hzrqlx cn Succeed 2/2 Jun 19,2025 18:21 UTC+0800 check ops status done ops_status:strent-hzrqlx-verticalscaling-k9vfc ns-riept VerticalScaling strent-hzrqlx cn Succeed 2/2 Jun 19,2025 18:21 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-hzrqlx-verticalscaling-k9vfc --namespace ns-riept ` opsrequest.apps.kubeblocks.io/strent-hzrqlx-verticalscaling-k9vfc patched `kbcli cluster delete-ops --name strent-hzrqlx-verticalscaling-k9vfc --force --auto-approve --namespace ns-riept ` OpsRequest strent-hzrqlx-verticalscaling-k9vfc deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value qmhav check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -- bash ` check db_client batch data Success cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop strent-hzrqlx --auto-approve --force=true --namespace ns-riept ` OpsRequest strent-hzrqlx-stop-nj72n created successfully, you can view the progress: kbcli cluster describe-ops strent-hzrqlx-stop-nj72n -n ns-riept check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-stop-nj72n ns-riept Stop strent-hzrqlx Creating -/- Jun 19,2025 18:22 UTC+0800 check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Stopping Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= 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 strent-hzrqlx --namespace ns-riept ` 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 strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-stop-nj72n ns-riept Stop strent-hzrqlx cn,fe Succeed 5/5 Jun 19,2025 18:22 UTC+0800 check ops status done ops_status:strent-hzrqlx-stop-nj72n ns-riept Stop strent-hzrqlx cn,fe Succeed 5/5 Jun 19,2025 18:22 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-hzrqlx-stop-nj72n --namespace ns-riept ` opsrequest.apps.kubeblocks.io/strent-hzrqlx-stop-nj72n patched `kbcli cluster delete-ops --name strent-hzrqlx-stop-nj72n --force --auto-approve --namespace ns-riept ` OpsRequest strent-hzrqlx-stop-nj72n deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start strent-hzrqlx --force=true --namespace ns-riept ` OpsRequest strent-hzrqlx-start-z5b6w created successfully, you can view the progress: kbcli cluster describe-ops strent-hzrqlx-start-z5b6w -n ns-riept check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-start-z5b6w ns-riept Start strent-hzrqlx Creating -/- Jun 19,2025 18:23 UTC+0800 check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Updating Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= 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 strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:24 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:24 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-10-205.us-west-2.compute.internal/172.31.10.205 Jun 19,2025 18:24 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:24 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1 / 1 2Gi / 2Gi data:20Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:24 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-start-z5b6w ns-riept Start strent-hzrqlx cn,fe Succeed 5/5 Jun 19,2025 18:23 UTC+0800 check ops status done ops_status:strent-hzrqlx-start-z5b6w ns-riept Start strent-hzrqlx cn,fe Succeed 5/5 Jun 19,2025 18:23 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-hzrqlx-start-z5b6w --namespace ns-riept ` opsrequest.apps.kubeblocks.io/strent-hzrqlx-start-z5b6w patched `kbcli cluster delete-ops --name strent-hzrqlx-start-z5b6w --force --auto-approve --namespace ns-riept ` OpsRequest strent-hzrqlx-start-z5b6w deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value qmhav check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -- bash ` check db_client batch data Success check component fe exists `kubectl get components -l app.kubernetes.io/instance=strent-hzrqlx,apps.kubeblocks.io/component-name=fe --namespace ns-riept | (grep "fe" || true )` cluster vscale check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale strent-hzrqlx --auto-approve --force=true --components fe --cpu 1100m --memory 2.1Gi --namespace ns-riept ` OpsRequest strent-hzrqlx-verticalscaling-7kzlk created successfully, you can view the progress: kbcli cluster describe-ops strent-hzrqlx-verticalscaling-7kzlk -n ns-riept check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-verticalscaling-7kzlk ns-riept VerticalScaling strent-hzrqlx fe Running 0/3 Jun 19,2025 18:25 UTC+0800 check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Updating Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= 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 strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:24 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:24 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi ip-172-31-10-205.us-west-2.compute.internal/172.31.10.205 Jun 19,2025 18:26 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:26 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:25 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-verticalscaling-7kzlk ns-riept VerticalScaling strent-hzrqlx fe Succeed 3/3 Jun 19,2025 18:25 UTC+0800 check ops status done ops_status:strent-hzrqlx-verticalscaling-7kzlk ns-riept VerticalScaling strent-hzrqlx fe Succeed 3/3 Jun 19,2025 18:25 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-hzrqlx-verticalscaling-7kzlk --namespace ns-riept ` opsrequest.apps.kubeblocks.io/strent-hzrqlx-verticalscaling-7kzlk patched `kbcli cluster delete-ops --name strent-hzrqlx-verticalscaling-7kzlk --force --auto-approve --namespace ns-riept ` OpsRequest strent-hzrqlx-verticalscaling-7kzlk deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value qmhav check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -- bash ` check db_client batch data Success cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart strent-hzrqlx --auto-approve --force=true --components cn --namespace ns-riept ` OpsRequest strent-hzrqlx-restart-2w59p created successfully, you can view the progress: kbcli cluster describe-ops strent-hzrqlx-restart-2w59p -n ns-riept check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-restart-2w59p ns-riept Restart strent-hzrqlx cn Running 0/2 Jun 19,2025 18:28 UTC+0800 check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Updating Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= 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 strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:28 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:28 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi ip-172-31-10-205.us-west-2.compute.internal/172.31.10.205 Jun 19,2025 18:26 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:26 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:25 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-restart-2w59p ns-riept Restart strent-hzrqlx cn Succeed 2/2 Jun 19,2025 18:28 UTC+0800 check ops status done ops_status:strent-hzrqlx-restart-2w59p ns-riept Restart strent-hzrqlx cn Succeed 2/2 Jun 19,2025 18:28 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-hzrqlx-restart-2w59p --namespace ns-riept ` opsrequest.apps.kubeblocks.io/strent-hzrqlx-restart-2w59p patched `kbcli cluster delete-ops --name strent-hzrqlx-restart-2w59p --force --auto-approve --namespace ns-riept ` OpsRequest strent-hzrqlx-restart-2w59p deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value qmhav check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -- bash ` check db_client batch data Success cluster hscale check cluster status before ops check cluster status done cluster_status:Running No resources found in strent-hzrqlx namespace. `kbcli cluster hscale strent-hzrqlx --auto-approve --force=true --components cn --replicas 3 --namespace ns-riept ` OpsRequest strent-hzrqlx-horizontalscaling-rd7bj created successfully, you can view the progress: kbcli cluster describe-ops strent-hzrqlx-horizontalscaling-rd7bj -n ns-riept check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-horizontalscaling-rd7bj ns-riept HorizontalScaling strent-hzrqlx cn Running 0/1 Jun 19,2025 18:29 UTC+0800 check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Updating Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= 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 strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:28 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:28 UTC+0800 strent-hzrqlx-cn-2 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-2-19.us-west-2.compute.internal/172.31.2.19 Jun 19,2025 18:29 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi ip-172-31-10-205.us-west-2.compute.internal/172.31.10.205 Jun 19,2025 18:26 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:26 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:25 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done No resources found in strent-hzrqlx namespace. check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-horizontalscaling-rd7bj ns-riept HorizontalScaling strent-hzrqlx cn Succeed 1/1 Jun 19,2025 18:29 UTC+0800 check ops status done ops_status:strent-hzrqlx-horizontalscaling-rd7bj ns-riept HorizontalScaling strent-hzrqlx cn Succeed 1/1 Jun 19,2025 18:29 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-hzrqlx-horizontalscaling-rd7bj --namespace ns-riept ` opsrequest.apps.kubeblocks.io/strent-hzrqlx-horizontalscaling-rd7bj patched `kbcli cluster delete-ops --name strent-hzrqlx-horizontalscaling-rd7bj --force --auto-approve --namespace ns-riept ` OpsRequest strent-hzrqlx-horizontalscaling-rd7bj deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value qmhav check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -- bash ` check db_client batch data Success skip ComponentName cn HorizontalScaling In skip Component cn VolumeExpansion check component fe exists `kubectl get components -l app.kubernetes.io/instance=strent-hzrqlx,apps.kubeblocks.io/component-name=fe --namespace ns-riept | (grep "fe" || true )` `kubectl get pvc -l app.kubernetes.io/instance=strent-hzrqlx,apps.kubeblocks.io/component-name=fe,apps.kubeblocks.io/vct-name=data --namespace ns-riept ` cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in strent-hzrqlx namespace. `kbcli cluster volume-expand strent-hzrqlx --auto-approve --force=true --components fe --volume-claim-templates data --storage 25Gi --namespace ns-riept ` OpsRequest strent-hzrqlx-volumeexpansion-twj48 created successfully, you can view the progress: kbcli cluster describe-ops strent-hzrqlx-volumeexpansion-twj48 -n ns-riept check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-volumeexpansion-twj48 ns-riept VolumeExpansion strent-hzrqlx fe Running 0/3 Jun 19,2025 18:31 UTC+0800 check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Updating Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= 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 strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:28 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:28 UTC+0800 strent-hzrqlx-cn-2 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-2-19.us-west-2.compute.internal/172.31.2.19 Jun 19,2025 18:29 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-10-205.us-west-2.compute.internal/172.31.10.205 Jun 19,2025 18:26 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:26 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:25 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done No resources found in strent-hzrqlx namespace. check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-volumeexpansion-twj48 ns-riept VolumeExpansion strent-hzrqlx fe Succeed 3/3 Jun 19,2025 18:31 UTC+0800 check ops status done ops_status:strent-hzrqlx-volumeexpansion-twj48 ns-riept VolumeExpansion strent-hzrqlx fe Succeed 3/3 Jun 19,2025 18:31 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-hzrqlx-volumeexpansion-twj48 --namespace ns-riept ` opsrequest.apps.kubeblocks.io/strent-hzrqlx-volumeexpansion-twj48 patched `kbcli cluster delete-ops --name strent-hzrqlx-volumeexpansion-twj48 --force --auto-approve --namespace ns-riept ` OpsRequest strent-hzrqlx-volumeexpansion-twj48 deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value qmhav check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -- bash ` check db_client batch data Success cluster rebulid instances apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: strent-hzrqlx-rebuildinstance- namespace: ns-riept spec: type: RebuildInstance clusterName: strent-hzrqlx force: true rebuildFrom: - componentName: cn instances: - name: strent-hzrqlx-cn-0 inPlace: true check cluster status before ops check cluster status done cluster_status:Running `kubectl create -f test_ops_cluster_strent-hzrqlx.yaml` opsrequest.apps.kubeblocks.io/strent-hzrqlx-rebuildinstance-xb82z created create test_ops_cluster_strent-hzrqlx.yaml Success `rm -rf test_ops_cluster_strent-hzrqlx.yaml` check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-rebuildinstance-xb82z ns-riept RebuildInstance strent-hzrqlx cn Running 0/1 Jun 19,2025 18:33 UTC+0800 ops_status:strent-hzrqlx-rebuildinstance-xb82z ns-riept RebuildInstance strent-hzrqlx cn Running 0/1 Jun 19,2025 18:33 UTC+0800 ops_status:strent-hzrqlx-rebuildinstance-xb82z ns-riept RebuildInstance strent-hzrqlx cn Running 0/1 Jun 19,2025 18:33 UTC+0800 ops_status:strent-hzrqlx-rebuildinstance-xb82z ns-riept RebuildInstance strent-hzrqlx cn Running 0/1 Jun 19,2025 18:33 UTC+0800 check ops status done ops_status:strent-hzrqlx-rebuildinstance-xb82z ns-riept RebuildInstance strent-hzrqlx cn Succeed 1/1 Jun 19,2025 18:33 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-hzrqlx-rebuildinstance-xb82z --namespace ns-riept ` opsrequest.apps.kubeblocks.io/strent-hzrqlx-rebuildinstance-xb82z patched `kbcli cluster delete-ops --name strent-hzrqlx-rebuildinstance-xb82z --force --auto-approve --namespace ns-riept ` OpsRequest strent-hzrqlx-rebuildinstance-xb82z deleted check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Running Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:33 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:28 UTC+0800 strent-hzrqlx-cn-2 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-2-19.us-west-2.compute.internal/172.31.2.19 Jun 19,2025 18:29 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-10-205.us-west-2.compute.internal/172.31.10.205 Jun 19,2025 18:26 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:26 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:25 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value qmhav check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -- bash ` check db_client batch data Success cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart strent-hzrqlx --auto-approve --force=true --namespace ns-riept ` OpsRequest strent-hzrqlx-restart-8k6r6 created successfully, you can view the progress: kbcli cluster describe-ops strent-hzrqlx-restart-8k6r6 -n ns-riept check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-restart-8k6r6 ns-riept Restart strent-hzrqlx fe,cn Running 0/6 Jun 19,2025 18:34 UTC+0800 check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Updating Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= 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 strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:36 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:35 UTC+0800 strent-hzrqlx-cn-2 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-2-19.us-west-2.compute.internal/172.31.2.19 Jun 19,2025 18:35 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-10-205.us-west-2.compute.internal/172.31.10.205 Jun 19,2025 18:36 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-1-25.us-west-2.compute.internal/172.31.1.25 Jun 19,2025 18:35 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:35 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-restart-8k6r6 ns-riept Restart strent-hzrqlx fe,cn Succeed 6/6 Jun 19,2025 18:34 UTC+0800 check ops status done ops_status:strent-hzrqlx-restart-8k6r6 ns-riept Restart strent-hzrqlx fe,cn Succeed 6/6 Jun 19,2025 18:34 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-hzrqlx-restart-8k6r6 --namespace ns-riept ` opsrequest.apps.kubeblocks.io/strent-hzrqlx-restart-8k6r6 patched `kbcli cluster delete-ops --name strent-hzrqlx-restart-8k6r6 --force --auto-approve --namespace ns-riept ` OpsRequest strent-hzrqlx-restart-8k6r6 deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value qmhav check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -- bash ` check db_client batch data Success check component fe exists `kubectl get components -l app.kubernetes.io/instance=strent-hzrqlx,apps.kubeblocks.io/component-name=fe --namespace ns-riept | (grep "fe" || true )` cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart strent-hzrqlx --auto-approve --force=true --components fe --namespace ns-riept ` OpsRequest strent-hzrqlx-restart-nvrhh created successfully, you can view the progress: kbcli cluster describe-ops strent-hzrqlx-restart-nvrhh -n ns-riept check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-restart-nvrhh ns-riept Restart strent-hzrqlx fe Running 0/3 Jun 19,2025 18:37 UTC+0800 check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Updating Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= 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 strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:36 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:35 UTC+0800 strent-hzrqlx-cn-2 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-2-19.us-west-2.compute.internal/172.31.2.19 Jun 19,2025 18:35 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-10-205.us-west-2.compute.internal/172.31.10.205 Jun 19,2025 18:39 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:38 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:37 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-restart-nvrhh ns-riept Restart strent-hzrqlx fe Succeed 3/3 Jun 19,2025 18:37 UTC+0800 check ops status done ops_status:strent-hzrqlx-restart-nvrhh ns-riept Restart strent-hzrqlx fe Succeed 3/3 Jun 19,2025 18:37 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-hzrqlx-restart-nvrhh --namespace ns-riept ` opsrequest.apps.kubeblocks.io/strent-hzrqlx-restart-nvrhh patched `kbcli cluster delete-ops --name strent-hzrqlx-restart-nvrhh --force --auto-approve --namespace ns-riept ` OpsRequest strent-hzrqlx-restart-nvrhh deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value qmhav check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -- bash ` check db_client batch data Success test failover connectionstress check node drain check node drain success Error from server (NotFound): pods "test-db-client-connectionstress-strent-hzrqlx" not found `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-connectionstress-strent-hzrqlx --namespace ns-riept ` Error from server (NotFound): pods "test-db-client-connectionstress-strent-hzrqlx" not found 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. Error from server (NotFound): pods "test-db-client-connectionstress-strent-hzrqlx" not found `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys apiVersion: v1 kind: Pod metadata: name: test-db-client-connectionstress-strent-hzrqlx namespace: ns-riept spec: containers: - name: test-dbclient imagePullPolicy: IfNotPresent image: docker.io/apecloud/dbclient:test args: - "--host" - "strent-hzrqlx-fe-fe.ns-riept.svc.cluster.local" - "--user" - "root" - "--password" - "pir8D7Z845" - "--port" - "9030" - "--database" - "sys" - "--dbtype" - "starrocks" - "--test" - "connectionstress" - "--connections" - "200" - "--duration" - "60" restartPolicy: Never `kubectl apply -f test-db-client-connectionstress-strent-hzrqlx.yaml` pod/test-db-client-connectionstress-strent-hzrqlx created apply test-db-client-connectionstress-strent-hzrqlx.yaml Success `rm -rf test-db-client-connectionstress-strent-hzrqlx.yaml` check pod status pod_status:NAME READY STATUS RESTARTS AGE test-db-client-connectionstress-strent-hzrqlx 1/1 Running 0 6s check pod test-db-client-connectionstress-strent-hzrqlx status done pod_status:NAME READY STATUS RESTARTS AGE test-db-client-connectionstress-strent-hzrqlx 0/1 Completed 0 11s check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks DoNotTerminate Running Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:36 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:35 UTC+0800 strent-hzrqlx-cn-2 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-2-19.us-west-2.compute.internal/172.31.2.19 Jun 19,2025 18:35 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-10-205.us-west-2.compute.internal/172.31.10.205 Jun 19,2025 18:39 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:38 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:37 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done --host strent-hzrqlx-fe-fe.ns-riept.svc.cluster.local --user root --password pir8D7Z845 --port 9030 --database sys --dbtype starrocks --test connectionstress --connections 200 --duration 60 SLF4J(I): Connected with provider of type [ch.qos.logback.classic.spi.LogbackServiceProvider] 10:40:55.557 [main] DEBUG com.clickhouse.jdbc.ClickHouseDriver -- ClickHouse Driver 0.0.0.0(JDBC: 0.0.0.0) registered Test Result: null Connection Information: Database Type: starrocks Host: strent-hzrqlx-fe-fe.ns-riept.svc.cluster.local Port: 9030 Database: sys Table: User: root Org: Access Mode: mysql Test Type: connectionstress Connection Count: 200 Duration: 60 seconds `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-connectionstress-strent-hzrqlx --namespace ns-riept ` pod/test-db-client-connectionstress-strent-hzrqlx patched (no change) 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 "test-db-client-connectionstress-strent-hzrqlx" force deleted check failover pod name failover pod name:strent-hzrqlx-cn-0 failover connectionstress Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value qmhav check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -- bash ` check db_client batch data Success cluster list-logs `kbcli cluster list-logs strent-hzrqlx --namespace ns-riept ` No log files found. You can enable the log feature with the kbcli command below. kbcli cluster update strent-hzrqlx --enable-all-logs=true --namespace ns-riept Error from server (NotFound): pods "strent-hzrqlx-cn-0" not found cluster logs `kbcli cluster logs strent-hzrqlx --tail 30 --namespace ns-riept ` Defaulted container "cn" out of: cn, nginx, lorry, config-manager, init-lorry (init) [2025-06-19 18:36:31] strent-hzrqlx-cn-0 is not in suspend list anymore, ready to start. [Thu Jun 19 18:36:31 CST 2025] Add myself (strent-hzrqlx-cn-0.strent-hzrqlx-cn-headless.ns-riept.svc.cluster.local:9050) into FE ... [Thu Jun 19 18:36:31 CST 2025] /etc/starrocks/cn/conf not exist or not a directory, ignore ... [Thu Jun 19 18:36:31 CST 2025] run start_cn.sh cluster update terminationPolicy WipeOut `kbcli cluster update strent-hzrqlx --termination-policy=WipeOut --namespace ns-riept ` cluster.apps.kubeblocks.io/strent-hzrqlx updated check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks WipeOut Running Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:36 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:35 UTC+0800 strent-hzrqlx-cn-2 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-2-19.us-west-2.compute.internal/172.31.2.19 Jun 19,2025 18:35 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-10-205.us-west-2.compute.internal/172.31.10.205 Jun 19,2025 18:39 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:38 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:37 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose strent-hzrqlx --auto-approve --force=true --type internet --enable false --components fe --namespace ns-riept ` OpsRequest strent-hzrqlx-expose-sdmnk created successfully, you can view the progress: kbcli cluster describe-ops strent-hzrqlx-expose-sdmnk -n ns-riept check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-expose-sdmnk ns-riept Expose strent-hzrqlx fe Running 0/1 Jun 19,2025 18:42 UTC+0800 check cluster status `kbcli cluster list strent-hzrqlx --show-labels --namespace ns-riept ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-hzrqlx ns-riept starrocks WipeOut Running Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=strent-hzrqlx,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-hzrqlx --namespace ns-riept ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-hzrqlx-cn-0 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:36 UTC+0800 strent-hzrqlx-cn-1 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-13-192.us-west-2.compute.internal/172.31.13.192 Jun 19,2025 18:35 UTC+0800 strent-hzrqlx-cn-2 ns-riept strent-hzrqlx cn Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m ip-172-31-2-19.us-west-2.compute.internal/172.31.2.19 Jun 19,2025 18:35 UTC+0800 strent-hzrqlx-fe-0 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-10-205.us-west-2.compute.internal/172.31.10.205 Jun 19,2025 18:39 UTC+0800 strent-hzrqlx-fe-1 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-12-10.us-west-2.compute.internal/172.31.12.10 Jun 19,2025 18:38 UTC+0800 strent-hzrqlx-fe-2 ns-riept strent-hzrqlx fe Running us-west-2a 1100m / 1100m 2254857830400m / 2254857830400m data:25Gi ip-172-31-8-60.us-west-2.compute.internal/172.31.8.60 Jun 19,2025 18:37 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-hzrqlx --status all --namespace ns-riept ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-hzrqlx-expose-sdmnk ns-riept Expose strent-hzrqlx fe Succeed 1/1 Jun 19,2025 18:42 UTC+0800 check ops status done ops_status:strent-hzrqlx-expose-sdmnk ns-riept Expose strent-hzrqlx fe Succeed 1/1 Jun 19,2025 18:42 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-hzrqlx-expose-sdmnk --namespace ns-riept ` opsrequest.apps.kubeblocks.io/strent-hzrqlx-expose-sdmnk patched `kbcli cluster delete-ops --name strent-hzrqlx-expose-sdmnk --force --auto-approve --namespace ns-riept ` OpsRequest strent-hzrqlx-expose-sdmnk deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 -c fe --namespace ns-riept -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value qmhav check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-hzrqlx` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-hzrqlx-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:pir8D7Z845;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-hzrqlx-fe-fe.ns-riept.svc.cluster.local -uroot -p'pir8D7Z845' " | kubectl exec -it strent-hzrqlx-fe-0 --namespace ns-riept -- bash ` check db_client batch data Success delete cluster strent-hzrqlx `kbcli cluster delete strent-hzrqlx --auto-approve --namespace ns-riept ` Cluster strent-hzrqlx deleted pod_info:strent-hzrqlx-cn-0 4/4 Running 0 6m39s strent-hzrqlx-cn-1 4/4 Running 0 7m9s strent-hzrqlx-cn-2 4/4 Running 0 7m52s strent-hzrqlx-fe-0 3/3 Running 0 4m5s strent-hzrqlx-fe-1 3/3 Running 0 4m44s strent-hzrqlx-fe-2 3/3 Running 0 5m23s pod_info:strent-hzrqlx-cn-0 4/4 Running 0 7m strent-hzrqlx-cn-1 4/4 Running 0 7m30s strent-hzrqlx-cn-2 4/4 Running 0 8m13s strent-hzrqlx-fe-0 3/3 Running 0 4m26s strent-hzrqlx-fe-1 3/3 Running 0 5m5s strent-hzrqlx-fe-2 3/3 Running 0 5m44s pod_info:strent-hzrqlx-cn-0 4/4 Running 0 7m26s strent-hzrqlx-cn-1 4/4 Running 0 7m56s strent-hzrqlx-cn-2 4/4 Running 0 8m39s strent-hzrqlx-fe-0 3/3 Running 0 4m52s strent-hzrqlx-fe-1 3/3 Running 0 5m31s strent-hzrqlx-fe-2 3/3 Running 0 6m10s pod_info:strent-hzrqlx-cn-0 4/4 Terminating 0 7m53s strent-hzrqlx-cn-1 4/4 Terminating 0 8m23s strent-hzrqlx-cn-2 4/4 Terminating 0 9m6s strent-hzrqlx-fe-0 3/3 Running 0 5m19s strent-hzrqlx-fe-1 3/3 Running 0 5m58s strent-hzrqlx-fe-2 3/3 Running 0 6m37s No resources found in ns-riept namespace. delete cluster pod done No resources found in ns-riept namespace. check cluster resource non-exist OK: pvc No resources found in ns-riept namespace. delete cluster done No resources found in ns-riept namespace. No resources found in ns-riept namespace. No resources found in ns-riept namespace. Starrocks Ent Test Suite All Done! --------------------------------------Starrocks Ent (Topology = shared-data Replicas 2) Test Result-------------------------------------- [PASSED]|[Create]|[Topology=shared-data;ComponentVersion=starrocks-be;ServiceVersion=3.2.2;]|[Description=Create a cluster with the specified topology shared-data and component version starrocks-be and service version 3.2.2] [PASSED]|[Connect]|[ComponentName=cn]|[Description=Connect to the cluster] [PASSED]|[AddData]|[Values=qmhav]|[Description=Add data to the cluster] [PASSED]|[Expose]|[Enable=true;TYPE=internet;ComponentName=fe]|[Description=Expose Enable the internet service with fe component] [PASSED]|[VerticalScaling]|[ComponentName=cn]|[Description=VerticalScaling the cluster specify component cn] [PASSED]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [PASSED]|[VerticalScaling]|[ComponentName=fe]|[Description=VerticalScaling the cluster specify component fe] [PASSED]|[Restart]|[ComponentName=cn]|[Description=Restart the cluster specify component cn] [PASSED]|[HorizontalScaling Out]|[ComponentName=cn]|[Description=HorizontalScaling Out the cluster specify component cn] [PASSED]|[VolumeExpansion]|[ComponentName=fe]|[Description=VolumeExpansion the cluster specify component fe] [PASSED]|[RebuildInstance]|[ComponentName=cn]|[Description=Rebuild the cluster instance specify component cn] [PASSED]|[Restart]|[-]|[Description=Restart the cluster] [PASSED]|[Restart]|[ComponentName=fe]|[Description=Restart the cluster specify component fe] [PASSED]|[Failover]|[HA=Connection Stress;ComponentName=cn]|[Description=Simulates conditions where pods experience connection stress either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to high Connection load.] [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut] [PASSED]|[Expose]|[Disable=true;TYPE=internet;ComponentName=fe]|[Description=Expose Disable the internet service with fe component] [PASSED]|[Delete]|[-]|[Description=Delete the cluster] [END]