source commons files source engines files source kubeblocks files `kubectl get namespace | grep ns-jvbdx ` `kubectl create namespace ns-jvbdx` namespace/ns-jvbdx created create namespace ns-jvbdx 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 104M 0 --:--:-- --:--:-- --:--:-- 104M 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 create etcd cluster etcdr-vwyqsa check cluster definition set component name:etcd LIMIT_CPU:0.1 LIMIT_MEMORY:0.5 storage size: 1 No resources found in ns-jvbdx namespace. create 3 replica WipeOut etcd cluster check cluster version check cluster definition `kbcli cluster create etcdr-vwyqsa --termination-policy=WipeOut --cluster-definition=etcd --enable-all-logs=false --cluster-version=etcd-v3.5.6 --set cpu=100m,memory=0.5Gi,replicas=3,storage=1Gi --namespace ns-jvbdx ` Cluster etcdr-vwyqsa created check cluster status `kbcli cluster list etcdr-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS etcdr-vwyqsa ns-jvbdx etcd etcd-v3.5.6 WipeOut Jun 19,2025 18:14 UTC+0800 clusterdefinition.kubeblocks.io/name=etcd,clusterversion.kubeblocks.io/name=etcd-v3.5.6 cluster_status:Creating cluster_status:Creating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances etcdr-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME etcdr-vwyqsa-etcd-0 ns-jvbdx etcdr-vwyqsa etcd Running follower us-west-2a 100m / 100m 512Mi / 512Mi data:1Gi ip-172-31-4-34.us-west-2.compute.internal/172.31.4.34 Jun 19,2025 18:14 UTC+0800 etcdr-vwyqsa-etcd-1 ns-jvbdx etcdr-vwyqsa etcd Running leader us-west-2a 100m / 100m 512Mi / 512Mi data:1Gi ip-172-31-2-196.us-west-2.compute.internal/172.31.2.196 Jun 19,2025 18:14 UTC+0800 etcdr-vwyqsa-etcd-2 ns-jvbdx etcdr-vwyqsa etcd Running follower us-west-2a 100m / 100m 512Mi / 512Mi data:1Gi ip-172-31-15-180.us-west-2.compute.internal/172.31.15.180 Jun 19,2025 18:14 UTC+0800 check pod status done check cluster role check cluster role done leader: etcdr-vwyqsa-etcd-1;follower: etcdr-vwyqsa-etcd-0 etcdr-vwyqsa-etcd-2 connect unsupported engine type: etcd `kubectl get secrets -l app.kubernetes.io/instance=etcdr-vwyqsa` `kubectl get secrets etcdr-vwyqsa-conn-credential -o jsonpath="***.data.username***"` `kubectl get secrets etcdr-vwyqsa-conn-credential -o jsonpath="***.data.password***"` `kubectl get secrets etcdr-vwyqsa-conn-credential -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:;DB_PORT:2379;DB_DATABASE: There is no password in Type: 15. get cluster endpoint SERVICE_CLUSTER_ENDPOINT:etcdr-vwyqsa-etcd.ns-jvbdx.svc.cluster.local:2379 check cluster definition set component name:frontend set component version No resources found no component version found unsupported component definition KUBEBLOCKS NAMESPACE:kb-paxuq get kubeblocks namespace done `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-paxuq -o jsonpath="***.items[0].data.root-user***"` `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-paxuq -o jsonpath="***.items[0].data.root-password***"` minio_user:kbclitest,minio_password:kbclitest,minio_endpoint:kbcli-test-minio.kb-paxuq.svc.cluster.local:9000 list minio bucket kbcli-test `echo 'mc config host add minioserver http://kbcli-test-minio.kb-paxuq.svc.cluster.local:9000 kbclitest kbclitest;mc ls minioserver' | kubectl exec -it kbcli-test-minio-5fbcd6864c-grqnp --namespace kb-paxuq -- bash` Unable to use a TTY - input is not a terminal or the right kind of file list minio bucket done not found component version set replicas first:2 set replicas third:2 set minimum cmpv service version set minimum cmpv service version replicas:2 REPORT_COUNT:1 CLUSTER_TOPOLOGY: Not found topology in cluster definition risingwave LIMIT_CPU:0.1 LIMIT_MEMORY:1 storage size: 1 No resources found in ns-jvbdx namespace. termination_policy:WipeOut create 2 replica WipeOut risingwave cluster check cluster version check cluster definition `kubectl apply -f test_create_risingw-vwyqsa.yaml` cluster.apps.kubeblocks.io/risingw-vwyqsa created apply test_create_risingw-vwyqsa.yaml Success `rm -rf test_create_risingw-vwyqsa.yaml` check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Jun 19,2025 18:16 UTC+0800 clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 cluster_status: cluster_status:Creating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-11-106.us-west-2.compute.internal/172.31.11.106 Jun 19,2025 18:16 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-5-116.us-west-2.compute.internal/172.31.5.116 Jun 19,2025 18:16 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:16 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:16 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-5-116.us-west-2.compute.internal/172.31.5.116 Jun 19,2025 18:16 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-3-195.us-west-2.compute.internal/172.31.3.195 Jun 19,2025 18:16 UTC+0800 check pod status done connect unsupported engine type: risingwave `kubectl get secrets -l app.kubernetes.io/instance=risingw-vwyqsa` `kubectl get secrets risingw-vwyqsa-conn-credential -o jsonpath="***.data.username***"` `kubectl get secrets risingw-vwyqsa-conn-credential -o jsonpath="***.data.password***"` `kubectl get secrets risingw-vwyqsa-conn-credential -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:;DB_PORT:2379;DB_DATABASE: There is no password in Type: 13. describe cluster `kbcli cluster describe risingw-vwyqsa --namespace ns-jvbdx ` Name: risingw-vwyqsa Created Time: Jun 19,2025 18:16 UTC+0800 NAMESPACE CLUSTER-DEFINITION VERSION STATUS TERMINATION-POLICY ns-jvbdx risingwave risingwave-v1.0.0 Running WipeOut Endpoints: COMPONENT MODE INTERNAL EXTERNAL frontend ReadWrite risingw-vwyqsa-frontend.ns-jvbdx.svc.cluster.local:4567 risingw-vwyqsa-frontend.ns-jvbdx.svc.cluster.local:8080 meta ReadWrite risingw-vwyqsa-meta.ns-jvbdx.svc.cluster.local:5690 risingw-vwyqsa-meta.ns-jvbdx.svc.cluster.local:5691 risingw-vwyqsa-meta.ns-jvbdx.svc.cluster.local:1250 compute ReadWrite risingw-vwyqsa-compute.ns-jvbdx.svc.cluster.local:5688 risingw-vwyqsa-compute.ns-jvbdx.svc.cluster.local:1222 compactor ReadWrite risingw-vwyqsa-compactor.ns-jvbdx.svc.cluster.local:6660 risingw-vwyqsa-compactor.ns-jvbdx.svc.cluster.local:1260 connector ReadWrite risingw-vwyqsa-connector.ns-jvbdx.svc.cluster.local:50051 risingw-vwyqsa-connector.ns-jvbdx.svc.cluster.local:50052 Topology: COMPONENT INSTANCE ROLE STATUS AZ NODE CREATED-TIME compactor risingw-vwyqsa-compactor-0 Running us-west-2a ip-172-31-11-106.us-west-2.compute.internal/172.31.11.106 Jun 19,2025 18:16 UTC+0800 compute risingw-vwyqsa-compute-0 Running us-west-2a ip-172-31-5-116.us-west-2.compute.internal/172.31.5.116 Jun 19,2025 18:16 UTC+0800 connector risingw-vwyqsa-connector-0 Running us-west-2a ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:16 UTC+0800 frontend risingw-vwyqsa-frontend-0 Running us-west-2a ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:16 UTC+0800 frontend risingw-vwyqsa-frontend-1 Running us-west-2a ip-172-31-5-116.us-west-2.compute.internal/172.31.5.116 Jun 19,2025 18:16 UTC+0800 meta risingw-vwyqsa-meta-0 Running us-west-2a ip-172-31-3-195.us-west-2.compute.internal/172.31.3.195 Jun 19,2025 18:16 UTC+0800 Resources Allocation: COMPONENT DEDICATED CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS frontend false 100m / 100m 1Gi / 1Gi meta false 100m / 100m 1Gi / 1Gi compute false 100m / 100m 1Gi / 1Gi compactor false 100m / 100m 1Gi / 1Gi connector false 100m / 100m 1Gi / 1Gi Images: COMPONENT TYPE IMAGE frontend frontend docker.io/apecloud/risingwave:v1.0.0 meta meta docker.io/apecloud/risingwave:v1.0.0 compute compute docker.io/apecloud/risingwave:v1.0.0 compactor compactor docker.io/apecloud/risingwave:v1.0.0 connector connector docker.io/apecloud/risingwave:v1.0.0 Show cluster events: kbcli cluster list-events -n ns-jvbdx risingw-vwyqsa `kbcli cluster label risingw-vwyqsa app.kubernetes.io/instance- --namespace ns-jvbdx ` label "app.kubernetes.io/instance" not found. `kbcli cluster label risingw-vwyqsa app.kubernetes.io/instance=risingw-vwyqsa --namespace ns-jvbdx ` `kbcli cluster label risingw-vwyqsa --list --namespace ns-jvbdx ` NAME NAMESPACE LABELS risingw-vwyqsa ns-jvbdx app.kubernetes.io/instance=risingw-vwyqsa clusterdefinition.kubeblocks.io/name=risingwave clusterversion.kubeblocks.io/name=risingwave-v1.0.0 label cluster app.kubernetes.io/instance=risingw-vwyqsa Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=risingw-vwyqsa --namespace ns-jvbdx ` `kbcli cluster label risingw-vwyqsa --list --namespace ns-jvbdx ` NAME NAMESPACE LABELS risingw-vwyqsa ns-jvbdx app.kubernetes.io/instance=risingw-vwyqsa case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=risingwave clusterversion.kubeblocks.io/name=risingwave-v1.0.0 label cluster case.name=kbcli.test1 Success `kbcli cluster label risingw-vwyqsa case.name=kbcli.test2 --overwrite --namespace ns-jvbdx ` `kbcli cluster label risingw-vwyqsa --list --namespace ns-jvbdx ` NAME NAMESPACE LABELS risingw-vwyqsa ns-jvbdx app.kubernetes.io/instance=risingw-vwyqsa case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=risingwave clusterversion.kubeblocks.io/name=risingwave-v1.0.0 label cluster case.name=kbcli.test2 Success `kbcli cluster label risingw-vwyqsa case.name- --namespace ns-jvbdx ` `kbcli cluster label risingw-vwyqsa --list --namespace ns-jvbdx ` NAME NAMESPACE LABELS risingw-vwyqsa ns-jvbdx app.kubernetes.io/instance=risingw-vwyqsa clusterdefinition.kubeblocks.io/name=risingwave clusterversion.kubeblocks.io/name=risingwave-v1.0.0 delete cluster label case.name Success cluster connect create psql-client pod risingw-vwyqsa-psql-client `kubectl run --namespace ns-jvbdx risingw-vwyqsa-psql-client --restart='Never' --image docker.io/apecloud/psql:latest --command -- sleep infinity` pod/risingw-vwyqsa-psql-client created check pod status pod_status:NAME READY STATUS RESTARTS AGE risingw-vwyqsa-psql-client 0/1 ContainerCreating 0 1s check pod risingw-vwyqsa-psql-client status done `kubectl wait --for=condition=Ready pod risingw-vwyqsa-psql-client --namespace ns-jvbdx` pod/risingw-vwyqsa-psql-client condition met pod_status:NAME READY STATUS RESTARTS AGE risingw-vwyqsa-psql-client 1/1 Running 0 6s `kubectl get secrets -l app.kubernetes.io/instance=risingw-vwyqsa` `kubectl get secrets risingw-vwyqsa-conn-credential -o jsonpath="***.data.username***"` `kubectl get secrets risingw-vwyqsa-conn-credential -o jsonpath="***.data.password***"` `kubectl get secrets risingw-vwyqsa-conn-credential -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:;DB_PORT:2379;DB_DATABASE: `kubectl get secrets risingw-vwyqsa-conn-credential -o jsonpath="***.data.endpoint***"` endpoints:risingw-vwyqsa-frontend:4567 `echo "echo 'select * from rw_catalog.rw_worker_nodes;create database if not exists benchtest;' | psql -h risingw-vwyqsa-frontend -p 4567 -d dev -U root" | kubectl exec -it risingw-vwyqsa-psql-client --namespace ns-jvbdx -- sh ` Unable to use a TTY - input is not a terminal or the right kind of file id | host | port | type | state | parallelism | is_streaming | is_serving | is_unschedulable ----+-----------------------------------------------------------------------+------+--------------+---------+-------------+--------------+------------+------------------ 3 | risingw-vwyqsa-compute-0.risingw-vwyqsa-compute-headless.ns-jvbdx.svc | 5688 | COMPUTE_NODE | RUNNING | 1 | t | t | f (1 row) CREATE_DATABASE connect cluster Success `kubectl delete pod risingw-vwyqsa-psql-client --force --namespace ns-jvbdx ` 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 "risingw-vwyqsa-psql-client" force deleted check component meta exists `kubectl get components -l app.kubernetes.io/instance=risingw-vwyqsa,apps.kubeblocks.io/component-name=meta --namespace ns-jvbdx | (grep "meta" || true )` cluster vscale check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale risingw-vwyqsa --auto-approve --force=true --components meta --cpu 200m --memory 1.1Gi --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-verticalscaling-7rtms created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-verticalscaling-7rtms -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-verticalscaling-7rtms ns-jvbdx VerticalScaling risingw-vwyqsa meta Running 0/1 Jun 19,2025 18:18 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Updating Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 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 risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-11-106.us-west-2.compute.internal/172.31.11.106 Jun 19,2025 18:16 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-5-116.us-west-2.compute.internal/172.31.5.116 Jun 19,2025 18:16 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:16 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:16 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-5-116.us-west-2.compute.internal/172.31.5.116 Jun 19,2025 18:16 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:19 UTC+0800 check pod status done connect unsupported engine type: risingwave check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-verticalscaling-7rtms ns-jvbdx VerticalScaling risingw-vwyqsa meta Succeed 1/1 Jun 19,2025 18:18 UTC+0800 check ops status done ops_status:risingw-vwyqsa-verticalscaling-7rtms ns-jvbdx VerticalScaling risingw-vwyqsa meta Succeed 1/1 Jun 19,2025 18:18 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-verticalscaling-7rtms --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-verticalscaling-7rtms patched `kbcli cluster delete-ops --name risingw-vwyqsa-verticalscaling-7rtms --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-verticalscaling-7rtms deleted check component frontend exists `kubectl get components -l app.kubernetes.io/instance=risingw-vwyqsa,apps.kubeblocks.io/component-name=frontend --namespace ns-jvbdx | (grep "frontend" || true )` check component compute exists `kubectl get components -l app.kubernetes.io/instance=risingw-vwyqsa,apps.kubeblocks.io/component-name=compute --namespace ns-jvbdx | (grep "compute" || true )` cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart risingw-vwyqsa --auto-approve --force=true --components frontend,compute --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-restart-6d6kb created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-restart-6d6kb -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-restart-6d6kb ns-jvbdx Restart risingw-vwyqsa frontend,compute Pending -/- Jun 19,2025 18:19 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Updating Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 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 risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-11-106.us-west-2.compute.internal/172.31.11.106 Jun 19,2025 18:16 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:20 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:16 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:20 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-5-116.us-west-2.compute.internal/172.31.5.116 Jun 19,2025 18:20 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:19 UTC+0800 check pod status done connect unsupported engine type: risingwave check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-restart-6d6kb ns-jvbdx Restart risingw-vwyqsa frontend,compute Succeed 3/3 Jun 19,2025 18:19 UTC+0800 check ops status done ops_status:risingw-vwyqsa-restart-6d6kb ns-jvbdx Restart risingw-vwyqsa frontend,compute Succeed 3/3 Jun 19,2025 18:19 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-restart-6d6kb --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-restart-6d6kb patched `kbcli cluster delete-ops --name risingw-vwyqsa-restart-6d6kb --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-restart-6d6kb deleted check component compactor exists `kubectl get components -l app.kubernetes.io/instance=risingw-vwyqsa,apps.kubeblocks.io/component-name=compactor --namespace ns-jvbdx | (grep "compactor" || true )` check component connector exists `kubectl get components -l app.kubernetes.io/instance=risingw-vwyqsa,apps.kubeblocks.io/component-name=connector --namespace ns-jvbdx | (grep "connector" || true )` cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart risingw-vwyqsa --auto-approve --force=true --components compactor,connector --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-restart-rgq67 created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-restart-rgq67 -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-restart-rgq67 ns-jvbdx Restart risingw-vwyqsa compactor,connector Running 0/2 Jun 19,2025 18:21 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Updating Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 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 risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:21 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:20 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:21 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:20 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-5-116.us-west-2.compute.internal/172.31.5.116 Jun 19,2025 18:20 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:19 UTC+0800 check pod status done connect unsupported engine type: risingwave check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-restart-rgq67 ns-jvbdx Restart risingw-vwyqsa compactor,connector Succeed 2/2 Jun 19,2025 18:21 UTC+0800 check ops status done ops_status:risingw-vwyqsa-restart-rgq67 ns-jvbdx Restart risingw-vwyqsa compactor,connector Succeed 2/2 Jun 19,2025 18:21 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-restart-rgq67 --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-restart-rgq67 patched `kbcli cluster delete-ops --name risingw-vwyqsa-restart-rgq67 --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-restart-rgq67 deleted cluster vscale check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale risingw-vwyqsa --auto-approve --force=true --components frontend --cpu 200m --memory 1.1Gi --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-verticalscaling-mgwhp created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-verticalscaling-mgwhp -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-verticalscaling-mgwhp ns-jvbdx VerticalScaling risingw-vwyqsa frontend Running 0/2 Jun 19,2025 18:23 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Updating Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 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 risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:21 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:20 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:21 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:24 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-5-116.us-west-2.compute.internal/172.31.5.116 Jun 19,2025 18:23 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:19 UTC+0800 check pod status done connect unsupported engine type: risingwave check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-verticalscaling-mgwhp ns-jvbdx VerticalScaling risingw-vwyqsa frontend Succeed 2/2 Jun 19,2025 18:23 UTC+0800 check ops status done ops_status:risingw-vwyqsa-verticalscaling-mgwhp ns-jvbdx VerticalScaling risingw-vwyqsa frontend Succeed 2/2 Jun 19,2025 18:23 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-verticalscaling-mgwhp --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-verticalscaling-mgwhp patched `kbcli cluster delete-ops --name risingw-vwyqsa-verticalscaling-mgwhp --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-verticalscaling-mgwhp deleted check component compactor exists `kubectl get components -l app.kubernetes.io/instance=risingw-vwyqsa,apps.kubeblocks.io/component-name=compactor --namespace ns-jvbdx | (grep "compactor" || true )` check component connector exists `kubectl get components -l app.kubernetes.io/instance=risingw-vwyqsa,apps.kubeblocks.io/component-name=connector --namespace ns-jvbdx | (grep "connector" || true )` cluster vscale check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale risingw-vwyqsa --auto-approve --force=true --components compactor,connector --cpu 200m --memory 1.1Gi --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-verticalscaling-5dc2r created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-verticalscaling-5dc2r -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-verticalscaling-5dc2r ns-jvbdx VerticalScaling risingw-vwyqsa compactor,connector Running 0/2 Jun 19,2025 18:24 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Updating Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 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 risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:25 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:20 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:25 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:24 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-5-116.us-west-2.compute.internal/172.31.5.116 Jun 19,2025 18:23 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:19 UTC+0800 check pod status done connect unsupported engine type: risingwave check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-verticalscaling-5dc2r ns-jvbdx VerticalScaling risingw-vwyqsa compactor,connector Succeed 2/2 Jun 19,2025 18:24 UTC+0800 check ops status done ops_status:risingw-vwyqsa-verticalscaling-5dc2r ns-jvbdx VerticalScaling risingw-vwyqsa compactor,connector Succeed 2/2 Jun 19,2025 18:24 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-verticalscaling-5dc2r --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-verticalscaling-5dc2r patched `kbcli cluster delete-ops --name risingw-vwyqsa-verticalscaling-5dc2r --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-verticalscaling-5dc2r deleted cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop risingw-vwyqsa --auto-approve --force=true --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-stop-sfssc created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-stop-sfssc -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-stop-sfssc ns-jvbdx Stop risingw-vwyqsa compactor,compute,connector,frontend,meta Running 0/6 Jun 19,2025 18:25 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Stopping Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 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 risingw-vwyqsa --namespace ns-jvbdx ` 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 risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-stop-sfssc ns-jvbdx Stop risingw-vwyqsa compactor,compute,connector,frontend,meta Succeed 6/6 Jun 19,2025 18:25 UTC+0800 check ops status done ops_status:risingw-vwyqsa-stop-sfssc ns-jvbdx Stop risingw-vwyqsa compactor,compute,connector,frontend,meta Succeed 6/6 Jun 19,2025 18:25 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-stop-sfssc --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-stop-sfssc patched `kbcli cluster delete-ops --name risingw-vwyqsa-stop-sfssc --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-stop-sfssc deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start risingw-vwyqsa --force=true --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-start-xcwzq created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-start-xcwzq -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-start-xcwzq ns-jvbdx Start risingw-vwyqsa compactor,compute,connector,frontend,meta Running 0/6 Jun 19,2025 18:27 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Updating Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:27 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:27 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:27 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:27 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:27 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:27 UTC+0800 check pod status done connect unsupported engine type: risingwave check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-start-xcwzq ns-jvbdx Start risingw-vwyqsa compactor,compute,connector,frontend,meta Succeed 6/6 Jun 19,2025 18:27 UTC+0800 check ops status done ops_status:risingw-vwyqsa-start-xcwzq ns-jvbdx Start risingw-vwyqsa compactor,compute,connector,frontend,meta Succeed 6/6 Jun 19,2025 18:27 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-start-xcwzq --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-start-xcwzq patched `kbcli cluster delete-ops --name risingw-vwyqsa-start-xcwzq --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-start-xcwzq deleted cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart risingw-vwyqsa --auto-approve --force=true --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-restart-f27l4 created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-restart-f27l4 -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-restart-f27l4 ns-jvbdx Restart risingw-vwyqsa frontend,meta,compute,compactor,connector Running 0/6 Jun 19,2025 18:27 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Updating Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 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 risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:29 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:28 UTC+0800 check pod status done connect unsupported engine type: risingwave check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-restart-f27l4 ns-jvbdx Restart risingw-vwyqsa frontend,meta,compute,compactor,connector Succeed 6/6 Jun 19,2025 18:27 UTC+0800 check ops status done ops_status:risingw-vwyqsa-restart-f27l4 ns-jvbdx Restart risingw-vwyqsa frontend,meta,compute,compactor,connector Succeed 6/6 Jun 19,2025 18:27 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-restart-f27l4 --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-restart-f27l4 patched `kbcli cluster delete-ops --name risingw-vwyqsa-restart-f27l4 --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-restart-f27l4 deleted check component meta exists `kubectl get components -l app.kubernetes.io/instance=risingw-vwyqsa,apps.kubeblocks.io/component-name=meta --namespace ns-jvbdx | (grep "meta" || true )` cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart risingw-vwyqsa --auto-approve --force=true --components meta --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-restart-t2tlr created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-restart-t2tlr -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-restart-t2tlr ns-jvbdx Restart risingw-vwyqsa meta Running 0/1 Jun 19,2025 18:29 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Updating Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 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 risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:29 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:30 UTC+0800 check pod status done connect unsupported engine type: risingwave check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-restart-t2tlr ns-jvbdx Restart risingw-vwyqsa meta Succeed 1/1 Jun 19,2025 18:29 UTC+0800 check ops status done ops_status:risingw-vwyqsa-restart-t2tlr ns-jvbdx Restart risingw-vwyqsa meta Succeed 1/1 Jun 19,2025 18:29 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-restart-t2tlr --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-restart-t2tlr patched `kbcli cluster delete-ops --name risingw-vwyqsa-restart-t2tlr --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-restart-t2tlr deleted cluster hscale check cluster status before ops check cluster status done cluster_status:Running No resources found in risingw-vwyqsa namespace. `kbcli cluster hscale risingw-vwyqsa --auto-approve --force=true --components frontend --replicas 3 --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-horizontalscaling-fq8dt created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-horizontalscaling-fq8dt -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-horizontalscaling-fq8dt ns-jvbdx HorizontalScaling risingw-vwyqsa frontend Running 0/1 Jun 19,2025 18:30 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Running Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:29 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-frontend-2 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-5-116.us-west-2.compute.internal/172.31.5.116 Jun 19,2025 18:30 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:30 UTC+0800 check pod status done connect unsupported engine type: risingwave No resources found in risingw-vwyqsa namespace. check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-horizontalscaling-fq8dt ns-jvbdx HorizontalScaling risingw-vwyqsa frontend Succeed 1/1 Jun 19,2025 18:30 UTC+0800 check ops status done ops_status:risingw-vwyqsa-horizontalscaling-fq8dt ns-jvbdx HorizontalScaling risingw-vwyqsa frontend Succeed 1/1 Jun 19,2025 18:30 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-horizontalscaling-fq8dt --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-horizontalscaling-fq8dt patched `kbcli cluster delete-ops --name risingw-vwyqsa-horizontalscaling-fq8dt --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-horizontalscaling-fq8dt deleted cluster hscale check cluster status before ops check cluster status done cluster_status:Running No resources found in risingw-vwyqsa namespace. `kbcli cluster hscale risingw-vwyqsa --auto-approve --force=true --components frontend --replicas 2 --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-horizontalscaling-cj8dr created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-horizontalscaling-cj8dr -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-horizontalscaling-cj8dr ns-jvbdx HorizontalScaling risingw-vwyqsa frontend Running 0/1 Jun 19,2025 18:31 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Updating Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 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 risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:29 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:30 UTC+0800 check pod status done connect unsupported engine type: risingwave No resources found in risingw-vwyqsa namespace. check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-horizontalscaling-cj8dr ns-jvbdx HorizontalScaling risingw-vwyqsa frontend Succeed 1/1 Jun 19,2025 18:31 UTC+0800 check ops status done ops_status:risingw-vwyqsa-horizontalscaling-cj8dr ns-jvbdx HorizontalScaling risingw-vwyqsa frontend Succeed 1/1 Jun 19,2025 18:31 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-horizontalscaling-cj8dr --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-horizontalscaling-cj8dr patched `kbcli cluster delete-ops --name risingw-vwyqsa-horizontalscaling-cj8dr --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-horizontalscaling-cj8dr deleted check component compute exists `kubectl get components -l app.kubernetes.io/instance=risingw-vwyqsa,apps.kubeblocks.io/component-name=compute --namespace ns-jvbdx | (grep "compute" || true )` cluster hscale check cluster status before ops check cluster status done cluster_status:Running No resources found in risingw-vwyqsa namespace. `kbcli cluster hscale risingw-vwyqsa --auto-approve --force=true --components compute --replicas 2 --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-horizontalscaling-gdq7h created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-horizontalscaling-gdq7h -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-horizontalscaling-gdq7h ns-jvbdx HorizontalScaling risingw-vwyqsa compute Running 0/1 Jun 19,2025 18:31 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Updating Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-compute-1 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-5-116.us-west-2.compute.internal/172.31.5.116 Jun 19,2025 18:31 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:29 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:30 UTC+0800 check pod status done connect unsupported engine type: risingwave No resources found in risingw-vwyqsa namespace. check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-horizontalscaling-gdq7h ns-jvbdx HorizontalScaling risingw-vwyqsa compute Succeed 1/1 Jun 19,2025 18:31 UTC+0800 check ops status done ops_status:risingw-vwyqsa-horizontalscaling-gdq7h ns-jvbdx HorizontalScaling risingw-vwyqsa compute Succeed 1/1 Jun 19,2025 18:31 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-horizontalscaling-gdq7h --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-horizontalscaling-gdq7h patched `kbcli cluster delete-ops --name risingw-vwyqsa-horizontalscaling-gdq7h --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-horizontalscaling-gdq7h deleted check component compute exists `kubectl get components -l app.kubernetes.io/instance=risingw-vwyqsa,apps.kubeblocks.io/component-name=compute --namespace ns-jvbdx | (grep "compute" || true )` cluster hscale check cluster status before ops check cluster status done cluster_status:Running No resources found in risingw-vwyqsa namespace. `kbcli cluster hscale risingw-vwyqsa --auto-approve --force=true --components compute --replicas 1 --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-horizontalscaling-rw557 created successfully, you can view the progress: kbcli cluster describe-ops risingw-vwyqsa-horizontalscaling-rw557 -n ns-jvbdx check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-horizontalscaling-rw557 ns-jvbdx HorizontalScaling risingw-vwyqsa compute Running 0/1 Jun 19,2025 18:32 UTC+0800 check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Updating Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 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 risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:29 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:30 UTC+0800 check pod status done connect unsupported engine type: risingwave No resources found in risingw-vwyqsa namespace. check ops status `kbcli cluster list-ops risingw-vwyqsa --status all --namespace ns-jvbdx ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME risingw-vwyqsa-horizontalscaling-rw557 ns-jvbdx HorizontalScaling risingw-vwyqsa compute Succeed 1/1 Jun 19,2025 18:32 UTC+0800 check ops status done ops_status:risingw-vwyqsa-horizontalscaling-rw557 ns-jvbdx HorizontalScaling risingw-vwyqsa compute Succeed 1/1 Jun 19,2025 18:32 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests risingw-vwyqsa-horizontalscaling-rw557 --namespace ns-jvbdx ` opsrequest.apps.kubeblocks.io/risingw-vwyqsa-horizontalscaling-rw557 patched `kbcli cluster delete-ops --name risingw-vwyqsa-horizontalscaling-rw557 --force --auto-approve --namespace ns-jvbdx ` OpsRequest risingw-vwyqsa-horizontalscaling-rw557 deleted cluster update terminationPolicy WipeOut `kbcli cluster update risingw-vwyqsa --termination-policy=WipeOut --namespace ns-jvbdx ` cluster.apps.kubeblocks.io/risingw-vwyqsa updated (no change) check cluster status `kbcli cluster list risingw-vwyqsa --show-labels --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS risingw-vwyqsa ns-jvbdx risingwave risingwave-v1.0.0 WipeOut Running Jun 19,2025 18:16 UTC+0800 app.kubernetes.io/instance=risingw-vwyqsa,clusterdefinition.kubeblocks.io/name=risingwave,clusterversion.kubeblocks.io/name=risingwave-v1.0.0 check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances risingw-vwyqsa --namespace ns-jvbdx ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME risingw-vwyqsa-compactor-0 ns-jvbdx risingw-vwyqsa compactor Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-compute-0 ns-jvbdx risingw-vwyqsa compute Running us-west-2a 100m / 100m 1Gi / 1Gi ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-connector-0 ns-jvbdx risingw-vwyqsa connector Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-frontend-0 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:29 UTC+0800 risingw-vwyqsa-frontend-1 ns-jvbdx risingw-vwyqsa frontend Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-15-105.us-west-2.compute.internal/172.31.15.105 Jun 19,2025 18:28 UTC+0800 risingw-vwyqsa-meta-0 ns-jvbdx risingw-vwyqsa meta Running us-west-2a 200m / 200m 1181116006400m / 1181116006400m ip-172-31-1-230.us-west-2.compute.internal/172.31.1.230 Jun 19,2025 18:30 UTC+0800 check pod status done connect unsupported engine type: risingwave cluster list-logs `kbcli cluster list-logs risingw-vwyqsa --namespace ns-jvbdx ` No log files found. You can enable the log feature with the kbcli command below. kbcli cluster update risingw-vwyqsa --enable-all-logs=true --namespace ns-jvbdx Error from server (NotFound): pods "risingw-vwyqsa-frontend-0" not found cluster logs `kbcli cluster logs risingw-vwyqsa --tail 30 --namespace ns-jvbdx ` 2025-06-19T10:30:08.159455876Z WARN risingwave_storage::hummock::compactor: Subscribing to compaction tasks failed with error: gRPC error (The service is currently unavailable): error trying to connect: tcp connect error: Connection refused (os error 111). Will retry. at src/storage/src/hummock/compactor/mod.rs:506 2025-06-19T10:30:08.186633246Z WARN risingwave_rpc_client::meta_client: refresh meta member client failed gRPC error (The service is currently unavailable): error trying to connect: tcp connect error: Connection refused (os error 111) at src/rpc_client/src/meta_client.rs:1449 2025-06-19T10:30:08.186701829Z WARN risingwave_rpc_client::meta_client: force refresh meta client failed gRPC error (The service is currently unavailable): error trying to connect: tcp connect error: Connection refused (os error 111) at src/rpc_client/src/meta_client.rs:1689 2025-06-19T10:30:11.909617702Z WARN risingwave_rpc_client::meta_client: Failed to send_heartbeat: timeout deadline has elapsed at src/rpc_client/src/meta_client.rs:655 2025-06-19T10:30:14.910946064Z WARN risingwave_rpc_client::meta_client: Failed to send_heartbeat: timeout deadline has elapsed at src/rpc_client/src/meta_client.rs:655 2025-06-19T10:30:16.808495561Z WARN risingwave_rpc_client::meta_client: refresh meta member client failed gRPC error (The service is currently unavailable): error trying to connect: deadline has elapsed at src/rpc_client/src/meta_client.rs:1449 2025-06-19T10:30:34.910018156Z DEBUG risingwave_storage::hummock::compactor: Succeeded subscribe_compact_tasks. at src/storage/src/hummock/compactor/mod.rs:502 2025-06-19T10:30:34.910983229Z DEBUG risingwave_storage::hummock::compactor: compactor cpu usage 4294967295 at src/storage/src/hummock/compactor/mod.rs:550 2025-06-19T10:31:34.911753154Z DEBUG risingwave_storage::hummock::compactor: compactor cpu usage 4294967295 at src/storage/src/hummock/compactor/mod.rs:550 2025-06-19T10:32:34.910601078Z DEBUG risingwave_storage::hummock::compactor: compactor cpu usage 4294967295 at src/storage/src/hummock/compactor/mod.rs:550 delete cluster risingw-vwyqsa `kbcli cluster delete risingw-vwyqsa --auto-approve --namespace ns-jvbdx ` Cluster risingw-vwyqsa deleted pod_info:risingw-vwyqsa-compactor-0 1/1 Running 0 5m11s risingw-vwyqsa-compute-0 1/1 Running 0 5m11s risingw-vwyqsa-connector-0 1/1 Running 0 5m11s risingw-vwyqsa-frontend-0 1/1 Running 0 4m29s risingw-vwyqsa-frontend-1 1/1 Running 0 5m12s risingw-vwyqsa-meta-0 1/1 Running 0 3m28s pod_info:risingw-vwyqsa-compactor-0 1/1 Terminating 0 5m32s risingw-vwyqsa-compute-0 1/1 Terminating 0 5m32s risingw-vwyqsa-connector-0 1/1 Terminating 0 5m32s risingw-vwyqsa-frontend-0 1/1 Terminating 0 4m50s risingw-vwyqsa-frontend-1 1/1 Terminating 0 5m33s risingw-vwyqsa-meta-0 1/1 Terminating 0 3m49s No resources found in ns-jvbdx namespace. delete cluster pod done No resources found in ns-jvbdx namespace. check cluster resource non-exist OK: pvc No resources found in ns-jvbdx namespace. delete cluster done No resources found in ns-jvbdx namespace. No resources found in ns-jvbdx namespace. No resources found in ns-jvbdx namespace. Risingwave Test Suite All Done! delete cluster etcdr-vwyqsa `kbcli cluster delete etcdr-vwyqsa --auto-approve --namespace ns-jvbdx ` Cluster etcdr-vwyqsa deleted pod_info:etcdr-vwyqsa-etcd-0 2/2 Terminating 0 19m etcdr-vwyqsa-etcd-1 2/2 Terminating 0 19m etcdr-vwyqsa-etcd-2 0/2 Completed 0 19m No resources found in ns-jvbdx namespace. delete cluster pod done No resources found in ns-jvbdx namespace. check cluster resource non-exist OK: pvc No resources found in ns-jvbdx namespace. delete cluster done No resources found in ns-jvbdx namespace. No resources found in ns-jvbdx namespace. No resources found in ns-jvbdx namespace. [PASSED]|[Create]|[ClusterDefinition=etcd;ClusterVersion=etcd-v3.5.6;]|[Description=Create a cluster with the specified cluster definition etcd and cluster version etcd-v3.5.6] --------------------------------------Risingwave (Topology = Replicas 2) Test Result-------------------------------------- [PASSED]|[Create]|[ClusterDefinition=risingwave;ClusterVersion=risingwave-v1.0.0;]|[Description=Create a cluster with the specified cluster definition risingwave and cluster version risingwave-v1.0.0] [PASSED]|[Connect]|[ComponentName=frontend]|[Description=Connect to the cluster] [PASSED]|[VerticalScaling]|[ComponentName=meta]|[Description=VerticalScaling the cluster specify component meta] [PASSED]|[Restart]|[ComponentName=frontend,compute]|[Description=Restart the cluster specify component frontend,compute] [PASSED]|[Restart]|[ComponentName=compactor,connector]|[Description=Restart the cluster specify component compactor,connector] [PASSED]|[VerticalScaling]|[ComponentName=frontend]|[Description=VerticalScaling the cluster specify component frontend] [PASSED]|[VerticalScaling]|[ComponentName=compactor,connector]|[Description=VerticalScaling the cluster specify component compactor,connector] [PASSED]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [PASSED]|[Restart]|[-]|[Description=Restart the cluster] [PASSED]|[Restart]|[ComponentName=meta]|[Description=Restart the cluster specify component meta] [PASSED]|[HorizontalScaling Out]|[ComponentName=frontend]|[Description=HorizontalScaling Out the cluster specify component frontend] [PASSED]|[HorizontalScaling In]|[ComponentName=frontend]|[Description=HorizontalScaling In the cluster specify component frontend] [PASSED]|[HorizontalScaling Out]|[ComponentName=compute]|[Description=HorizontalScaling Out the cluster specify component compute] [PASSED]|[HorizontalScaling In]|[ComponentName=compute]|[Description=HorizontalScaling In the cluster specify component compute] [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut] [PASSED]|[Delete]|[-]|[Description=Delete the cluster] [END]