https://github.com/apecloud/kubeblocks/actions/runs/21898070919 previous_version: kubeblocks_version:1.0.2 bash test/kbcli/test_kbcli_1.0.sh --type 68 --version 1.0.2 --generate-output true --chaos-mesh true --aws-access-key-id *** --aws-secret-access-key *** --jihulab-token *** --random-namespace true --region eastus --cloud-provider aks CURRENT_TEST_DIR:test/kbcli source commons files source engines files source kubeblocks files source kubedb files CLUSTER_NAME:  `kubectl get namespace | grep ns-ptjas `(B   `kubectl create namespace ns-ptjas`(B  namespace/ns-ptjas created create namespace ns-ptjas done(B check registry secret create docker registry server https://index.docker.io/v1/ secret/kbcli-test-registry-key created create docker registry secret kbcli-test-registry-key Success(B check ns:ns-ptjas sa:default imagePullSecrets patch ns:ns-ptjas sa:default imagePullSecrets serviceaccount/default patched patch ns:ns-ptjas sa:default imagePullSecrets Success(B download kbcli  `gh release list --repo apecloud/kbcli --limit 100 | (grep "1.0" || true)`(B   `curl -fsSL https://kubeblocks.io/installer/install_cli.sh | bash -s v1.0.2`(B  Your system is linux_amd64 Installing kbcli ... Downloading ... Failed to unpack kbcli executable. Failed to install kbcli Go to https://kubeblocks.io for more support. checking kbcli next...(B  `gh release list --repo apecloud/kbcli --limit 100 | (grep "1.0" || true)`(B  ignore kbcli v1.0.2(B ignore kbcli v1.0.2(B  `curl -fsSL https://kubeblocks.io/installer/install_cli.sh | bash -s v1.0.2-beta.0`(B  Your system is linux_amd64 Installing kbcli ... Downloading ... kbcli installed successfully. Kubernetes: v1.32.10 KubeBlocks: 1.0.2 kbcli: 1.0.2-beta.0 Make sure your docker service is running and begin your journey with kbcli: kbcli playground init For more information on how to get started, please visit: https://kubeblocks.io download kbcli v1.0.2-beta.0 done(B Kubernetes: v1.32.10 KubeBlocks: 1.0.2 kbcli: 1.0.2-beta.0 Kubernetes Env: v1.32.10 check snapshot controller check snapshot controller done(B POD_RESOURCES: aks kb-default-sc found aks default-vsc found found default storage class: default (B KubeBlocks version is:1.0.2 skip upgrade KubeBlocks(B current KubeBlocks version: 1.0.2 helm repo add chaos-mesh https://charts.chaos-mesh.org "chaos-mesh" has been added to your repositories add helm chart repo chaos-mesh success chaos mesh already installed check component definition check component definition set component name:namenode set component version set component version:hadoop set service versions:3.3.6,3.3.1 set service versions sorted:3.3.1,3.3.6 set hadoop component definition set hadoop component definition hadoop-hdfs-datanode-1.0.2 REPORT_COUNT 0:0 set replicas first:2,3.3.1|2,3.3.6 set replicas third:2,3.3.6 set replicas fourth:2,3.3.1 set minimum cmpv service version set minimum cmpv service version replicas:2,3.3.1 set replicas end:2,3.3.1 REPORT_COUNT:1 CLUSTER_TOPOLOGY:ha-cluster cluster definition topology: hdfs-cluster ha-cluster ha-ref-zk-cluster topology ha-cluster found in cluster definition hadoop set hadoop component definition set hadoop component definition hadoop-hdfs-datanode-1.0.2 LIMIT_CPU:0.5 LIMIT_MEMORY:1 storage size: 20 CLUSTER_NAME:hadoop-tjnzau pod_info: termination_policy:Delete create 2 replica Delete hadoop cluster check component definition set component definition by component version check cmpd by labels check cmpd by compDefs set component definition: hadoop-hdfs-datanode-1.0.2 by component version:hadoop apiVersion: v1 kind: ConfigMap metadata: name: hadoop-tjnzau-namenode-hosts namespace: ns-ptjas labels: app.kubernetes.io/name: hadoop-tjnzau app.kubernetes.io/component: namenode data: hosts.exclude: "" --- apiVersion: apps.kubeblocks.io/v1 kind: Cluster metadata: name: hadoop-tjnzau namespace: ns-ptjas spec: clusterDef: hadoop topology: ha-cluster terminationPolicy: Delete componentSpecs: - name: namenode serviceVersion: 3.3.1 replicas: 2 resources: limits: cpu: 500m memory: 1Gi requests: cpu: 500m memory: 1Gi volumes: - name: hadoop-core-config configMap: name: hadoop-tjnzau-journalnode-core-config - name: hosts-config configMap: name: hadoop-tjnzau-namenode-hosts volumeClaimTemplates: - name: metadata-dir spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: datanode replicas: 3 serviceVersion: 3.3.1 resources: limits: cpu: 500m memory: 1Gi requests: cpu: 500m memory: 1Gi volumes: - name: hadoop-core-config configMap: name: hadoop-tjnzau-journalnode-core-config volumeClaimTemplates: - name: data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 30Gi - name: journalnode serviceVersion: 3.3.1 replicas: 1 resources: limits: cpu: 500m memory: 1Gi requests: cpu: 500m memory: 1Gi volumeClaimTemplates: - name: edits-dir spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: resourcemanager replicas: 2 serviceVersion: 3.3.1 resources: limits: cpu: 500m memory: 3Gi requests: cpu: 500m memory: 3Gi volumes: - name: hadoop-core-config configMap: name: hadoop-tjnzau-journalnode-core-config - name: hadoop-namenode-config configMap: name: hadoop-tjnzau-namenode-config volumeClaimTemplates: - name: resourcemanager spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: nodemanager replicas: 1 serviceVersion: 3.3.1 resources: limits: cpu: 500m memory: 3Gi requests: cpu: 500m memory: 3Gi volumes: - name: hadoop-core-config configMap: name: hadoop-tjnzau-journalnode-core-config - name: hadoop-namenode-config configMap: name: hadoop-tjnzau-namenode-config - name: mapred-site-config configMap: name: hadoop-tjnzau-resourcemanager-mapred-site-config volumeClaimTemplates: - name: nodemanager spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: zookeeper serviceVersion: 3.9.2 replicas: 1 resources: limits: cpu: 500m memory: 1Gi requests: cpu: 500m memory: 1Gi volumeClaimTemplates: - name: data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: snapshot-log spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi  `kubectl apply -f test_create_hadoop-tjnzau.yaml`(B  configmap/hadoop-tjnzau-namenode-hosts created cluster.apps.kubeblocks.io/hadoop-tjnzau created apply test_create_hadoop-tjnzau.yaml Success(B  `rm -rf test_create_hadoop-tjnzau.yaml`(B  check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Creating Feb 11,2026 16:56 UTC+0800 clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Creating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:57 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:04 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 16:56 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2  `kubectl get secrets -l app.kubernetes.io/instance=hadoop-tjnzau`(B   `kubectl get secrets hadoop-tjnzau-zookeeper-account-admin -o jsonpath="{.data.username}"`(B   `kubectl get secrets hadoop-tjnzau-zookeeper-account-admin -o jsonpath="{.data.password}"`(B   `kubectl get secrets hadoop-tjnzau-zookeeper-account-admin -o jsonpath="{.data.port}"`(B  DB_USERNAME:hadoop;DB_PASSWORD:6JgUB025VzKSqpuJ;DB_PORT:8020;DB_DATABASE:(B check pod hadoop-tjnzau-namenode-0 container_name hdfs-namenode exist password 6JgUB025VzKSqpuJ(B check pod hadoop-tjnzau-namenode-0 container_name kbagent exist password 6JgUB025VzKSqpuJ(B No container logs contain secret password.(B describe cluster  `kbcli cluster describe hadoop-tjnzau --namespace ns-ptjas `(B  Name: hadoop-tjnzau Created Time: Feb 11,2026 16:56 UTC+0800 NAMESPACE CLUSTER-DEFINITION TOPOLOGY STATUS TERMINATION-POLICY ns-ptjas hadoop ha-cluster Running Delete Endpoints: COMPONENT INTERNAL EXTERNAL zookeeper hadoop-tjnzau-zookeeper.ns-ptjas.svc.cluster.local:2181 hadoop-tjnzau-zookeeper.ns-ptjas.svc.cluster.local:2888 hadoop-tjnzau-zookeeper.ns-ptjas.svc.cluster.local:8080 hadoop-tjnzau-zookeeper-readable.ns-ptjas.svc.cluster.local:2181 hadoop-tjnzau-zookeeper-readable.ns-ptjas.svc.cluster.local:2888 hadoop-tjnzau-zookeeper-readable.ns-ptjas.svc.cluster.local:8080 journalnode hadoop-tjnzau-journalnode.ns-ptjas.svc.cluster.local:8485 hadoop-tjnzau-journalnode.ns-ptjas.svc.cluster.local:8480 namenode hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:9870 resourcemanager hadoop-tjnzau-resourcemanager-resourcemanager.ns-ptjas.svc.cluster.local:8088 Topology: COMPONENT SERVICE-VERSION INSTANCE ROLE STATUS AZ NODE CREATED-TIME datanode 3.3.1 hadoop-tjnzau-datanode-0 Running 0 aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:00 UTC+0800 datanode 3.3.1 hadoop-tjnzau-datanode-1 Running 0 aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:00 UTC+0800 datanode 3.3.1 hadoop-tjnzau-datanode-2 Running 0 aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:00 UTC+0800 journalnode 3.3.1 hadoop-tjnzau-journalnode-0 Running 0 aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:57 UTC+0800 namenode 3.3.1 hadoop-tjnzau-namenode-0 active Running 0 aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:59 UTC+0800 namenode 3.3.1 hadoop-tjnzau-namenode-1 standby Running 0 aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 16:59 UTC+0800 nodemanager 3.3.1 hadoop-tjnzau-nodemanager-0 Running 0 aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:04 UTC+0800 resourcemanager 3.3.1 hadoop-tjnzau-resourcemanager-0 active Running 0 aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:02 UTC+0800 resourcemanager 3.3.1 hadoop-tjnzau-resourcemanager-1 standby Running 0 aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:02 UTC+0800 zookeeper 3.9.2 hadoop-tjnzau-zookeeper-0 leader Running 0 aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 16:56 UTC+0800 Resources Allocation: COMPONENT INSTANCE-TEMPLATE CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS zookeeper 500m / 500m 1Gi / 1Gi data:20Gi default snapshot-log:20Gi default journalnode 500m / 500m 1Gi / 1Gi edits-dir:20Gi default namenode 500m / 500m 1Gi / 1Gi metadata-dir:20Gi default datanode 500m / 500m 1Gi / 1Gi data:30Gi default resourcemanager 500m / 500m 3Gi / 3Gi resourcemanager:20Gi default nodemanager 500m / 500m 3Gi / 3Gi nodemanager:20Gi default Images: COMPONENT COMPONENT-DEFINITION IMAGE zookeeper zookeeper-1.0.2 docker.io/apecloud/zookeeper:3.9.2 journalnode hadoop-hdfs-journalnode-1.0.2 docker.io/apecloud/hadoop-common:3.3.1 namenode hadoop-hdfs-namenode-1.0.2 docker.io/apecloud/hadoop-common:3.3.1 datanode hadoop-hdfs-datanode-1.0.2 docker.io/apecloud/hadoop-common:3.3.1 resourcemanager hadoop-yarn-resourcemanager-1.0.2 docker.io/apecloud/hadoop-common:3.3.1 nodemanager hadoop-yarn-nodemanager-1.0.2 docker.io/apecloud/hadoop-common:3.3.1 Data Protection: BACKUP-REPO AUTO-BACKUP BACKUP-SCHEDULE BACKUP-METHOD BACKUP-RETENTION RECOVERABLE-TIME Show cluster events: kbcli cluster list-events -n ns-ptjas hadoop-tjnzau  `kbcli cluster label hadoop-tjnzau app.kubernetes.io/instance- --namespace ns-ptjas `(B  label "app.kubernetes.io/instance" not found.  `kbcli cluster label hadoop-tjnzau app.kubernetes.io/instance=hadoop-tjnzau --namespace ns-ptjas `(B   `kbcli cluster label hadoop-tjnzau --list --namespace ns-ptjas `(B  NAME NAMESPACE LABELS hadoop-tjnzau ns-ptjas app.kubernetes.io/instance=hadoop-tjnzau clusterdefinition.kubeblocks.io/name=hadoop label cluster app.kubernetes.io/instance=hadoop-tjnzau Success(B  `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=hadoop-tjnzau --namespace ns-ptjas `(B   `kbcli cluster label hadoop-tjnzau --list --namespace ns-ptjas `(B  NAME NAMESPACE LABELS hadoop-tjnzau ns-ptjas app.kubernetes.io/instance=hadoop-tjnzau case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=hadoop label cluster case.name=kbcli.test1 Success(B  `kbcli cluster label hadoop-tjnzau case.name=kbcli.test2 --overwrite --namespace ns-ptjas `(B   `kbcli cluster label hadoop-tjnzau --list --namespace ns-ptjas `(B  NAME NAMESPACE LABELS hadoop-tjnzau ns-ptjas app.kubernetes.io/instance=hadoop-tjnzau case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=hadoop label cluster case.name=kbcli.test2 Success(B  `kbcli cluster label hadoop-tjnzau case.name- --namespace ns-ptjas `(B   `kbcli cluster label hadoop-tjnzau --list --namespace ns-ptjas `(B  NAME NAMESPACE LABELS hadoop-tjnzau ns-ptjas app.kubernetes.io/instance=hadoop-tjnzau clusterdefinition.kubeblocks.io/name=hadoop delete cluster label case.name Success(B cluster connect insert batch data by db client  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge pods test-db-client-executionloop-hadoop-tjnzau --namespace ns-ptjas `(B   `kubectl get secrets -l app.kubernetes.io/instance=hadoop-tjnzau`(B   `kubectl get secrets hadoop-tjnzau-zookeeper-account-admin -o jsonpath="{.data.username}"`(B   `kubectl get secrets hadoop-tjnzau-zookeeper-account-admin -o jsonpath="{.data.password}"`(B   `kubectl get secrets hadoop-tjnzau-zookeeper-account-admin -o jsonpath="{.data.port}"`(B  DB_USERNAME:hadoop;DB_PASSWORD:6JgUB025VzKSqpuJ;DB_PORT:8020;DB_DATABASE:(B apiVersion: v1 kind: Pod metadata: name: test-db-client-executionloop-hadoop-tjnzau namespace: ns-ptjas spec: containers: - name: test-dbclient imagePullPolicy: IfNotPresent image: docker.io/apecloud/dbclient:test args: - "--host" - "hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local" - "--user" - "hadoop" - "--password" - "6JgUB025VzKSqpuJ" - "--port" - "8020" - "--dbtype" - "hadoop" - "--test" - "executionloop" - "--duration" - "60" - "--interval" - "1" restartPolicy: Never  `kubectl apply -f test-db-client-executionloop-hadoop-tjnzau.yaml`(B  pod/test-db-client-executionloop-hadoop-tjnzau created apply test-db-client-executionloop-hadoop-tjnzau.yaml Success(B  `rm -rf test-db-client-executionloop-hadoop-tjnzau.yaml`(B  check pod status pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 1/1 Running 0 6s(B pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 1/1 Running 0 10s(B pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 1/1 Running 0 15s(B pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 1/1 Running 0 20s(B pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 1/1 Running 0 26s(B pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 1/1 Running 0 31s(B pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 1/1 Running 0 36s(B pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 1/1 Running 0 41s(B pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 1/1 Running 0 47s(B pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 1/1 Running 0 52s(B pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 1/1 Running 0 57s(B pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 1/1 Running 0 62s(B check pod test-db-client-executionloop-hadoop-tjnzau status done(B pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-hadoop-tjnzau 0/1 Completed 0 68s(B check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Running Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:57 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:04 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 16:56 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 --host hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local --user hadoop --password 6JgUB025VzKSqpuJ --port 8020 --dbtype hadoop --test executionloop --duration 60 --interval 1 SLF4J(I): Connected with provider of type [ch.qos.logback.classic.spi.LogbackServiceProvider] 09:12:40.221 [main] WARN o.a.hadoop.util.NativeCodeLoader - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable Execution loop start: Creating database (directory) executions_loop Creating table (directory) executions_loop_table Execution loop start:Write data to /executions_loop/executions_loop_table/data_1.txt [ 1s ] executions total: 2 successful: 2 failed: 0 disconnect: 0 [ 2s ] executions total: 22 successful: 22 failed: 0 disconnect: 0 [ 3s ] executions total: 51 successful: 51 failed: 0 disconnect: 0 [ 4s ] executions total: 76 successful: 76 failed: 0 disconnect: 0 [ 5s ] executions total: 102 successful: 102 failed: 0 disconnect: 0 [ 6s ] executions total: 127 successful: 127 failed: 0 disconnect: 0 [ 7s ] executions total: 153 successful: 153 failed: 0 disconnect: 0 [ 8s ] executions total: 180 successful: 180 failed: 0 disconnect: 0 [ 9s ] executions total: 205 successful: 205 failed: 0 disconnect: 0 [ 10s ] executions total: 235 successful: 235 failed: 0 disconnect: 0 [ 11s ] executions total: 263 successful: 263 failed: 0 disconnect: 0 [ 12s ] executions total: 295 successful: 295 failed: 0 disconnect: 0 [ 13s ] executions total: 319 successful: 319 failed: 0 disconnect: 0 [ 14s ] executions total: 349 successful: 349 failed: 0 disconnect: 0 [ 15s ] executions total: 379 successful: 379 failed: 0 disconnect: 0 [ 16s ] executions total: 407 successful: 407 failed: 0 disconnect: 0 [ 17s ] executions total: 432 successful: 432 failed: 0 disconnect: 0 [ 18s ] executions total: 462 successful: 462 failed: 0 disconnect: 0 [ 19s ] executions total: 493 successful: 493 failed: 0 disconnect: 0 [ 20s ] executions total: 526 successful: 526 failed: 0 disconnect: 0 [ 21s ] executions total: 559 successful: 559 failed: 0 disconnect: 0 [ 22s ] executions total: 586 successful: 586 failed: 0 disconnect: 0 [ 23s ] executions total: 616 successful: 616 failed: 0 disconnect: 0 [ 24s ] executions total: 644 successful: 644 failed: 0 disconnect: 0 [ 25s ] executions total: 673 successful: 673 failed: 0 disconnect: 0 [ 26s ] executions total: 703 successful: 703 failed: 0 disconnect: 0 [ 27s ] executions total: 730 successful: 730 failed: 0 disconnect: 0 [ 28s ] executions total: 739 successful: 739 failed: 0 disconnect: 0 [ 29s ] executions total: 773 successful: 773 failed: 0 disconnect: 0 [ 30s ] executions total: 802 successful: 802 failed: 0 disconnect: 0 [ 31s ] executions total: 832 successful: 832 failed: 0 disconnect: 0 [ 32s ] executions total: 862 successful: 862 failed: 0 disconnect: 0 [ 33s ] executions total: 896 successful: 896 failed: 0 disconnect: 0 [ 34s ] executions total: 932 successful: 932 failed: 0 disconnect: 0 [ 35s ] executions total: 947 successful: 947 failed: 0 disconnect: 0 [ 36s ] executions total: 974 successful: 974 failed: 0 disconnect: 0 [ 37s ] executions total: 994 successful: 994 failed: 0 disconnect: 0 [ 38s ] executions total: 1025 successful: 1025 failed: 0 disconnect: 0 [ 39s ] executions total: 1054 successful: 1054 failed: 0 disconnect: 0 [ 40s ] executions total: 1070 successful: 1070 failed: 0 disconnect: 0 [ 41s ] executions total: 1087 successful: 1087 failed: 0 disconnect: 0 [ 42s ] executions total: 1117 successful: 1117 failed: 0 disconnect: 0 [ 43s ] executions total: 1148 successful: 1148 failed: 0 disconnect: 0 [ 44s ] executions total: 1181 successful: 1181 failed: 0 disconnect: 0 [ 45s ] executions total: 1215 successful: 1215 failed: 0 disconnect: 0 [ 46s ] executions total: 1252 successful: 1252 failed: 0 disconnect: 0 [ 47s ] executions total: 1281 successful: 1281 failed: 0 disconnect: 0 [ 48s ] executions total: 1314 successful: 1314 failed: 0 disconnect: 0 [ 49s ] executions total: 1342 successful: 1342 failed: 0 disconnect: 0 [ 50s ] executions total: 1368 successful: 1368 failed: 0 disconnect: 0 [ 51s ] executions total: 1401 successful: 1401 failed: 0 disconnect: 0 [ 52s ] executions total: 1439 successful: 1439 failed: 0 disconnect: 0 [ 53s ] executions total: 1471 successful: 1471 failed: 0 disconnect: 0 [ 54s ] executions total: 1504 successful: 1504 failed: 0 disconnect: 0 [ 55s ] executions total: 1535 successful: 1535 failed: 0 disconnect: 0 [ 56s ] executions total: 1566 successful: 1566 failed: 0 disconnect: 0 [ 57s ] executions total: 1606 successful: 1606 failed: 0 disconnect: 0 [ 58s ] executions total: 1641 successful: 1641 failed: 0 disconnect: 0 [ 60s ] executions total: 1661 successful: 1661 failed: 0 disconnect: 0 Test Result: Total Executions: 1661 Successful Executions: 1661 Failed Executions: 0 Disconnection Counts: 0 Connection Information: Database Type: hadoop Host: hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local Port: 8020 Database: Table: User: hadoop Org: Access Mode: mysql Test Type: executionloop Query: Duration: 60 seconds Interval: 1 seconds DB_CLIENT_BATCH_DATA_COUNT: 1661  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge pods test-db-client-executionloop-hadoop-tjnzau --namespace ns-ptjas `(B  pod/test-db-client-executionloop-hadoop-tjnzau patched (no change) pod "test-db-client-executionloop-hadoop-tjnzau" force deleted set db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  set db_client batch data Success(B check component namenode exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=namenode --namespace ns-ptjas | (grep "namenode" || true )`(B  check component datanode exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=datanode --namespace ns-ptjas | (grep "datanode" || true )`(B  check component journalnod exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=journalnod --namespace ns-ptjas | (grep "journalnod" || true )`(B  journalnod is not exists(B skip VerticalScaling component namenode,datanode,journalnod(B  `kubectl get pvc -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=namenode,apps.kubeblocks.io/vct-name=metadata-dir --namespace ns-ptjas `(B  cluster volume-expand check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster volume-expand hadoop-tjnzau --auto-approve --force=true --components namenode --volume-claim-templates metadata-dir --storage 25Gi --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-volumeexpansion-2vnw7 created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-volumeexpansion-2vnw7 -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-volumeexpansion-2vnw7 ns-ptjas VolumeExpansion hadoop-tjnzau namenode Running 0/2 Feb 11,2026 17:14 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:57 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:04 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 16:56 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-volumeexpansion-2vnw7 ns-ptjas VolumeExpansion hadoop-tjnzau namenode Succeed 2/2 Feb 11,2026 17:14 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-volumeexpansion-2vnw7 ns-ptjas VolumeExpansion hadoop-tjnzau namenode Succeed 2/2 Feb 11,2026 17:14 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-volumeexpansion-2vnw7 --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-volumeexpansion-2vnw7 patched  `kbcli cluster delete-ops --name hadoop-tjnzau-volumeexpansion-2vnw7 --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-volumeexpansion-2vnw7 deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component nodemanager exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=nodemanager --namespace ns-ptjas | (grep "nodemanager" || true )`(B  cluster nodemanager scale-out cluster nodemanager scale-out replicas: 3 check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster scale-out hadoop-tjnzau --auto-approve --force=true --components nodemanager --replicas 1 --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-czj2t created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-horizontalscaling-czj2t -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-czj2t ns-ptjas HorizontalScaling hadoop-tjnzau nodemanager Running 0/1 Feb 11,2026 17:27 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:57 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:04 UTC+0800 hadoop-tjnzau-nodemanager-1 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:27 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 16:56 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-czj2t ns-ptjas HorizontalScaling hadoop-tjnzau nodemanager Succeed 1/1 Feb 11,2026 17:27 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-horizontalscaling-czj2t ns-ptjas HorizontalScaling hadoop-tjnzau nodemanager Succeed 1/1 Feb 11,2026 17:27 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-horizontalscaling-czj2t --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-horizontalscaling-czj2t patched  `kbcli cluster delete-ops --name hadoop-tjnzau-horizontalscaling-czj2t --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-czj2t deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component nodemanager exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=nodemanager --namespace ns-ptjas | (grep "nodemanager" || true )`(B  cluster nodemanager scale-in cluster nodemanager scale-in replicas: 2 check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster scale-in hadoop-tjnzau --auto-approve --force=true --components nodemanager --replicas 1 --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-6x6hr created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-horizontalscaling-6x6hr -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-6x6hr ns-ptjas HorizontalScaling hadoop-tjnzau nodemanager Running 0/1 Feb 11,2026 17:31 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Running Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:57 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:04 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 16:56 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-6x6hr ns-ptjas HorizontalScaling hadoop-tjnzau nodemanager Succeed 1/1 Feb 11,2026 17:31 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-horizontalscaling-6x6hr ns-ptjas HorizontalScaling hadoop-tjnzau nodemanager Succeed 1/1 Feb 11,2026 17:31 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-horizontalscaling-6x6hr --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-horizontalscaling-6x6hr patched  `kbcli cluster delete-ops --name hadoop-tjnzau-horizontalscaling-6x6hr --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-6x6hr deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component resourcemanager exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=resourcemanager --namespace ns-ptjas | (grep "resourcemanager" || true )`(B   `kubectl get pvc -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=resourcemanager,apps.kubeblocks.io/vct-name=resourcemanager --namespace ns-ptjas `(B  cluster volume-expand check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster volume-expand hadoop-tjnzau --auto-approve --force=true --components resourcemanager --volume-claim-templates resourcemanager --storage 22Gi --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-volumeexpansion-l27sc created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-volumeexpansion-l27sc -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-volumeexpansion-l27sc ns-ptjas VolumeExpansion hadoop-tjnzau resourcemanager Running -/- Feb 11,2026 17:32 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:57 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:04 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 16:56 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-volumeexpansion-l27sc ns-ptjas VolumeExpansion hadoop-tjnzau resourcemanager Succeed 2/2 Feb 11,2026 17:32 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-volumeexpansion-l27sc ns-ptjas VolumeExpansion hadoop-tjnzau resourcemanager Succeed 2/2 Feb 11,2026 17:32 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-volumeexpansion-l27sc --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-volumeexpansion-l27sc patched  `kbcli cluster delete-ops --name hadoop-tjnzau-volumeexpansion-l27sc --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-volumeexpansion-l27sc deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component nodemanager exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=nodemanager --namespace ns-ptjas | (grep "nodemanager" || true )`(B   `kubectl get pvc -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=nodemanager,apps.kubeblocks.io/vct-name=nodemanager --namespace ns-ptjas `(B  cluster volume-expand check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster volume-expand hadoop-tjnzau --auto-approve --force=true --components nodemanager --volume-claim-templates nodemanager --storage 21Gi --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-volumeexpansion-jfknc created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-volumeexpansion-jfknc -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-volumeexpansion-jfknc ns-ptjas VolumeExpansion hadoop-tjnzau nodemanager Running 0/1 Feb 11,2026 17:36 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:00 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:20Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:57 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 16:59 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:04 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:02 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 16:56 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-volumeexpansion-jfknc ns-ptjas VolumeExpansion hadoop-tjnzau nodemanager Succeed 1/1 Feb 11,2026 17:36 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-volumeexpansion-jfknc ns-ptjas VolumeExpansion hadoop-tjnzau nodemanager Succeed 1/1 Feb 11,2026 17:36 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-volumeexpansion-jfknc --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-volumeexpansion-jfknc patched  `kbcli cluster delete-ops --name hadoop-tjnzau-volumeexpansion-jfknc --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-volumeexpansion-jfknc deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B cluster stop check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster stop hadoop-tjnzau --auto-approve --force=true --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-stop-cbmg5 created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-stop-cbmg5 -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-stop-cbmg5 ns-ptjas Stop hadoop-tjnzau datanode,journalnode,namenode,nodemanager,resourcemanager,zookeeper Running 0/10 Feb 11,2026 17:43 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Stopped Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop check cluster status done(B cluster_status:Stopped(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME check pod status done(B check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-stop-cbmg5 ns-ptjas Stop hadoop-tjnzau datanode,journalnode,namenode,nodemanager,resourcemanager,zookeeper Succeed 10/10 Feb 11,2026 17:43 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-stop-cbmg5 ns-ptjas Stop hadoop-tjnzau datanode,journalnode,namenode,nodemanager,resourcemanager,zookeeper Succeed 10/10 Feb 11,2026 17:43 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-stop-cbmg5 --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-stop-cbmg5 patched  `kbcli cluster delete-ops --name hadoop-tjnzau-stop-cbmg5 --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-stop-cbmg5 deleted cluster start check cluster status before ops check cluster status done(B cluster_status:Stopped(B  `kbcli cluster start hadoop-tjnzau --force=true --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-start-zs8w7 created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-start-zs8w7 -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-start-zs8w7 ns-ptjas Start hadoop-tjnzau datanode,journalnode,namenode,nodemanager,resourcemanager,zookeeper Running 0/10 Feb 11,2026 17:43 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1;standby(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-start-zs8w7 ns-ptjas Start hadoop-tjnzau datanode,journalnode,namenode,nodemanager,resourcemanager,zookeeper Succeed 10/10 Feb 11,2026 17:43 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-start-zs8w7 ns-ptjas Start hadoop-tjnzau datanode,journalnode,namenode,nodemanager,resourcemanager,zookeeper Succeed 10/10 Feb 11,2026 17:43 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-start-zs8w7 --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-start-zs8w7 patched  `kbcli cluster delete-ops --name hadoop-tjnzau-start-zs8w7 --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-start-zs8w7 deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-1 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component datanode exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=datanode --namespace ns-ptjas | (grep "datanode" || true )`(B  cluster datanode scale-out cluster datanode scale-out replicas: 3 check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster scale-out hadoop-tjnzau --auto-approve --force=true --components datanode --replicas 1 --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-5xqm2 created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-horizontalscaling-5xqm2 -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-5xqm2 ns-ptjas HorizontalScaling hadoop-tjnzau datanode Running 0/1 Feb 11,2026 17:48 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:48 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1;standby(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-5xqm2 ns-ptjas HorizontalScaling hadoop-tjnzau datanode Succeed 1/1 Feb 11,2026 17:48 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-horizontalscaling-5xqm2 ns-ptjas HorizontalScaling hadoop-tjnzau datanode Succeed 1/1 Feb 11,2026 17:48 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-horizontalscaling-5xqm2 --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-horizontalscaling-5xqm2 patched  `kbcli cluster delete-ops --name hadoop-tjnzau-horizontalscaling-5xqm2 --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-5xqm2 deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-1 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component namenode exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=namenode --namespace ns-ptjas | (grep "namenode" || true )`(B  check component datanode exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=datanode --namespace ns-ptjas | (grep "datanode" || true )`(B  cluster restart check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster restart hadoop-tjnzau --auto-approve --force=true --components namenode,datanode --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-restart-mvft6 created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-restart-mvft6 -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-restart-mvft6 ns-ptjas Restart hadoop-tjnzau namenode,datanode Running 0/6 Feb 11,2026 17:50 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:52 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-1;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-0 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-restart-mvft6 ns-ptjas Restart hadoop-tjnzau namenode,datanode Succeed 6/6 Feb 11,2026 17:50 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-restart-mvft6 ns-ptjas Restart hadoop-tjnzau namenode,datanode Succeed 6/6 Feb 11,2026 17:50 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-restart-mvft6 --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-restart-mvft6 patched  `kbcli cluster delete-ops --name hadoop-tjnzau-restart-mvft6 --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-restart-mvft6 deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component resourcemanager exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=resourcemanager --namespace ns-ptjas | (grep "resourcemanager" || true )`(B  check component nodemanager exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=nodemanager --namespace ns-ptjas | (grep "nodemanager" || true )`(B  cluster restart check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster restart hadoop-tjnzau --auto-approve --force=true --components resourcemanager,nodemanager --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-restart-tkngr created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-restart-tkngr -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-restart-tkngr ns-ptjas Restart hadoop-tjnzau resourcemanager,nodemanager Running 0/3 Feb 11,2026 17:53 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:52 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:20Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:53 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:53 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:53 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-restart-tkngr ns-ptjas Restart hadoop-tjnzau resourcemanager,nodemanager Succeed 3/3 Feb 11,2026 17:53 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-restart-tkngr ns-ptjas Restart hadoop-tjnzau resourcemanager,nodemanager Succeed 3/3 Feb 11,2026 17:53 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-restart-tkngr --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-restart-tkngr patched  `kbcli cluster delete-ops --name hadoop-tjnzau-restart-tkngr --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-restart-tkngr deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component journalnode exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=journalnode --namespace ns-ptjas | (grep "journalnode" || true )`(B   `kubectl get pvc -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=journalnode,apps.kubeblocks.io/vct-name=edits-dir --namespace ns-ptjas `(B  cluster volume-expand check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster volume-expand hadoop-tjnzau --auto-approve --force=true --components journalnode --volume-claim-templates edits-dir --storage 23Gi --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-volumeexpansion-m7g8t created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-volumeexpansion-m7g8t -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-volumeexpansion-m7g8t ns-ptjas VolumeExpansion hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 17:54 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:52 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:23Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:53 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:53 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:53 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-volumeexpansion-m7g8t ns-ptjas VolumeExpansion hadoop-tjnzau journalnode Succeed 1/1 Feb 11,2026 17:54 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-volumeexpansion-m7g8t ns-ptjas VolumeExpansion hadoop-tjnzau journalnode Succeed 1/1 Feb 11,2026 17:54 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-volumeexpansion-m7g8t --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-volumeexpansion-m7g8t patched  `kbcli cluster delete-ops --name hadoop-tjnzau-volumeexpansion-m7g8t --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-volumeexpansion-m7g8t deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component resourcemanager exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=resourcemanager --namespace ns-ptjas | (grep "resourcemanager" || true )`(B  cluster resourcemanager scale-out cluster resourcemanager scale-out replicas: 5 check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster scale-out hadoop-tjnzau --auto-approve --force=true --components resourcemanager --replicas 2 --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-54r8m created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-horizontalscaling-54r8m -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-54r8m ns-ptjas HorizontalScaling hadoop-tjnzau resourcemanager Running 0/2 Feb 11,2026 18:00 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:52 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:23Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:00 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:53 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:53 UTC+0800 hadoop-tjnzau-resourcemanager-2 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:00 UTC+0800 hadoop-tjnzau-resourcemanager-3 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:00 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 hadoop-tjnzau-resourcemanager-2 hadoop-tjnzau-resourcemanager-3 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-54r8m ns-ptjas HorizontalScaling hadoop-tjnzau resourcemanager Succeed 2/2 Feb 11,2026 18:00 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-horizontalscaling-54r8m ns-ptjas HorizontalScaling hadoop-tjnzau resourcemanager Succeed 2/2 Feb 11,2026 18:00 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-horizontalscaling-54r8m --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-horizontalscaling-54r8m patched  `kbcli cluster delete-ops --name hadoop-tjnzau-horizontalscaling-54r8m --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-54r8m deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component resourcemanager exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=resourcemanager --namespace ns-ptjas | (grep "resourcemanager" || true )`(B  cluster resourcemanager scale-in cluster resourcemanager scale-in replicas: 3 check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster scale-in hadoop-tjnzau --auto-approve --force=true --components resourcemanager --replicas 2 --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-xbwl5 created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-horizontalscaling-xbwl5 -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-xbwl5 ns-ptjas HorizontalScaling hadoop-tjnzau resourcemanager Running 0/2 Feb 11,2026 18:01 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:52 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:30Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:23Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:01 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:53 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:01 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-xbwl5 ns-ptjas HorizontalScaling hadoop-tjnzau resourcemanager Succeed 2/2 Feb 11,2026 18:01 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-horizontalscaling-xbwl5 ns-ptjas HorizontalScaling hadoop-tjnzau resourcemanager Succeed 2/2 Feb 11,2026 18:01 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-horizontalscaling-xbwl5 --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-horizontalscaling-xbwl5 patched  `kbcli cluster delete-ops --name hadoop-tjnzau-horizontalscaling-xbwl5 --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-xbwl5 deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component datanode exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=datanode --namespace ns-ptjas | (grep "datanode" || true )`(B   `kubectl get pvc -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=datanode,apps.kubeblocks.io/vct-name=data --namespace ns-ptjas `(B  cluster volume-expand check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster volume-expand hadoop-tjnzau --auto-approve --force=true --components datanode --volume-claim-templates data --storage 34Gi --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-volumeexpansion-vjl4z created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-volumeexpansion-vjl4z -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-volumeexpansion-vjl4z ns-ptjas VolumeExpansion hadoop-tjnzau datanode Running 0/4 Feb 11,2026 18:02 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:52 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:23Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:01 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:53 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:01 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-volumeexpansion-vjl4z ns-ptjas VolumeExpansion hadoop-tjnzau datanode Succeed 4/4 Feb 11,2026 18:02 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-volumeexpansion-vjl4z ns-ptjas VolumeExpansion hadoop-tjnzau datanode Succeed 4/4 Feb 11,2026 18:02 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-volumeexpansion-vjl4z --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-volumeexpansion-vjl4z patched  `kbcli cluster delete-ops --name hadoop-tjnzau-volumeexpansion-vjl4z --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-volumeexpansion-vjl4z deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component journalnode exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=journalnode --namespace ns-ptjas | (grep "journalnode" || true )`(B  cluster journalnode scale-out cluster journalnode scale-out replicas: 4 cluster full-journalnode backup  `kubectl get backuprepo backuprepo-kbcli-test -o jsonpath="{.spec.credential.name}"`(B   `kubectl get backuprepo backuprepo-kbcli-test -o jsonpath="{.spec.credential.namespace}"`(B   `kubectl get secrets kb-backuprepo-wd8pp -n kb-qepkz -o jsonpath="{.data.accessKeyId}"`(B   `kubectl get secrets kb-backuprepo-wd8pp -n kb-qepkz -o jsonpath="{.data.secretAccessKey}"`(B  KUBEBLOCKS NAMESPACE:kb-qepkz get kubeblocks namespace done(B  `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-qepkz -o jsonpath="{.items[0].data.root-user}"`(B   `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-qepkz -o jsonpath="{.items[0].data.root-password}"`(B  minio_user:kbclitest,minio_password:kbclitest,minio_endpoint:kbcli-test-minio.kb-qepkz.svc.cluster.local:9000 list minio bucket kbcli-test  `echo 'mc alias set minioserver http://kbcli-test-minio.kb-qepkz.svc.cluster.local:9000 kbclitest kbclitest;mc ls minioserver' | kubectl exec -it kbcli-test-minio-6b5dd49d-pvfs4 --namespace kb-qepkz -- bash`(B  list minio bucket done(B default backuprepo:backuprepo-kbcli-test exists(B get journalnode backup policy get backup policy:hadoop-tjnzau-journalnode-backup-policy success  `kbcli cluster backup hadoop-tjnzau --method full-journalnode --policy hadoop-tjnzau-journalnode-backup-policy --namespace ns-ptjas `(B  Backup backup-ns-ptjas-hadoop-tjnzau-20260211180818 created successfully, you can view the progress: kbcli cluster list-backups --names=backup-ns-ptjas-hadoop-tjnzau-20260211180818 -n ns-ptjas check backup status  `kbcli cluster list-backups hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE SOURCE-CLUSTER METHOD STATUS TOTAL-SIZE DURATION DELETION-POLICY CREATE-TIME COMPLETION-TIME EXPIRATION backup-ns-ptjas-hadoop-tjnzau-20260211180818 ns-ptjas hadoop-tjnzau full-journalnode Completed 111271 5s Delete Feb 11,2026 18:08 UTC+0800 Feb 11,2026 18:08 UTC+0800 get backup name BACKUP_NAME:backup-ns-ptjas-hadoop-tjnzau-20260211180818 check backup status done(B backup_status:backup-ns-ptjas-hadoop-tjnzau-20260211180818 ns-ptjas hadoop-tjnzau full-journalnode Completed 111271 5s Delete Feb 11,2026 18:08 UTC+0800 Feb 11,2026 18:08 UTC+0800 (B apiVersion: operations.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: hadoop-tjnzau-horizontalscaling- labels: app.kubernetes.io/instance: hadoop-tjnzau app.kubernetes.io/managed-by: kubeblocks namespace: ns-ptjas spec: type: HorizontalScaling clusterName: hadoop-tjnzau force: true horizontalScaling: - componentName: journalnode scaleOut: replicaChanges: 1 fromBackup: name: backup-ns-ptjas-hadoop-tjnzau-20260211180818 check cluster status before ops check cluster status done(B cluster_status:Running(B  `kubectl create -f test_ops_cluster_hadoop-tjnzau.yaml`(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-horizontalscaling-s2qmd created create test_ops_cluster_hadoop-tjnzau.yaml Success(B  `rm -rf test_ops_cluster_hadoop-tjnzau.yaml`(B  check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME backup-ns-ptjas-hadoop-tjnzau-20260211180818 ns-ptjas Backup hadoop-tjnzau Succeed -/- Feb 11,2026 18:08 UTC+0800 hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Running Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:52 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:23Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:01 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:53 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:01 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME backup-ns-ptjas-hadoop-tjnzau-20260211180818 ns-ptjas Backup hadoop-tjnzau Succeed -/- Feb 11,2026 18:08 UTC+0800 hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:08 UTC+0800 (B check ops status done(B ops_status:hadoop-tjnzau-horizontalscaling-s2qmd ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Succeed 1/1 Feb 11,2026 18:08 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-horizontalscaling-s2qmd --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-horizontalscaling-s2qmd patched  `kbcli cluster delete-ops --name hadoop-tjnzau-horizontalscaling-s2qmd --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-s2qmd deleted cluster delete backup  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge backups backup-ns-ptjas-hadoop-tjnzau-20260211180818 --namespace ns-ptjas `(B  backup.dataprotection.kubeblocks.io/backup-ns-ptjas-hadoop-tjnzau-20260211180818 patched  `kbcli cluster delete-backup hadoop-tjnzau --name backup-ns-ptjas-hadoop-tjnzau-20260211180818 --force --auto-approve --namespace ns-ptjas `(B  Backup backup-ns-ptjas-hadoop-tjnzau-20260211180818 deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component journalnode exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=journalnode --namespace ns-ptjas | (grep "journalnode" || true )`(B  cluster journalnode scale-in cluster journalnode scale-in replicas: 3 check cluster status before ops cluster_status:Updating(B check cluster status done(B cluster_status:Running(B  `kbcli cluster scale-in hadoop-tjnzau --auto-approve --force=true --components journalnode --replicas 1 --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-phjc6 created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-horizontalscaling-phjc6 -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-phjc6 ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Running 0/1 Feb 11,2026 18:10 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:52 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:51 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:23Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 17:43 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:50 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:10 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:01 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 17:53 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:01 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 17:43 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-phjc6 ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Succeed 1/1 Feb 11,2026 18:10 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-horizontalscaling-phjc6 ns-ptjas HorizontalScaling hadoop-tjnzau journalnode Succeed 1/1 Feb 11,2026 18:10 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-horizontalscaling-phjc6 --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-horizontalscaling-phjc6 patched  `kbcli cluster delete-ops --name hadoop-tjnzau-horizontalscaling-phjc6 --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-phjc6 deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-0 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component zookeeper exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=zookeeper --namespace ns-ptjas | (grep "zookeeper" || true )`(B  check component journalnod exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=journalnod --namespace ns-ptjas | (grep "journalnod" || true )`(B  journalnod is not exists(B skip Restart component zookeeper,journalnod(B cluster restart check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster restart hadoop-tjnzau --auto-approve --force=true --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-restart-lgk6k created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-restart-lgk6k -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-restart-lgk6k ns-ptjas Restart hadoop-tjnzau zookeeper,journalnode,namenode,datanode,resourcemanager,nodemanager Creating -/- Feb 11,2026 18:11 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:13 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:13 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:12 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:23Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:12 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:12 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1;standby(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-restart-lgk6k ns-ptjas Restart hadoop-tjnzau zookeeper,journalnode,namenode,datanode,resourcemanager,nodemanager Succeed 11/11 Feb 11,2026 18:11 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-restart-lgk6k ns-ptjas Restart hadoop-tjnzau zookeeper,journalnode,namenode,datanode,resourcemanager,nodemanager Succeed 11/11 Feb 11,2026 18:11 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-restart-lgk6k --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-restart-lgk6k patched  `kbcli cluster delete-ops --name hadoop-tjnzau-restart-lgk6k --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-restart-lgk6k deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-1 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B cluster namenode scale-out cluster namenode scale-out replicas: 5 cluster full-namenode backup  `kubectl get backuprepo backuprepo-kbcli-test -o jsonpath="{.spec.credential.name}"`(B   `kubectl get backuprepo backuprepo-kbcli-test -o jsonpath="{.spec.credential.namespace}"`(B   `kubectl get secrets kb-backuprepo-wd8pp -n kb-qepkz -o jsonpath="{.data.accessKeyId}"`(B   `kubectl get secrets kb-backuprepo-wd8pp -n kb-qepkz -o jsonpath="{.data.secretAccessKey}"`(B  KUBEBLOCKS NAMESPACE:kb-qepkz get kubeblocks namespace done(B  `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-qepkz -o jsonpath="{.items[0].data.root-user}"`(B   `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-qepkz -o jsonpath="{.items[0].data.root-password}"`(B  minio_user:kbclitest,minio_password:kbclitest,minio_endpoint:kbcli-test-minio.kb-qepkz.svc.cluster.local:9000 list minio bucket kbcli-test  `echo 'mc alias set minioserver http://kbcli-test-minio.kb-qepkz.svc.cluster.local:9000 kbclitest kbclitest;mc ls minioserver' | kubectl exec -it kbcli-test-minio-6b5dd49d-pvfs4 --namespace kb-qepkz -- bash`(B  list minio bucket done(B default backuprepo:backuprepo-kbcli-test exists(B get namenode backup policy get backup policy:hadoop-tjnzau-namenode-backup-policy success  `kbcli cluster backup hadoop-tjnzau --method full-namenode --policy hadoop-tjnzau-namenode-backup-policy --namespace ns-ptjas `(B  Backup backup-ns-ptjas-hadoop-tjnzau-20260211181453 created successfully, you can view the progress: kbcli cluster list-backups --names=backup-ns-ptjas-hadoop-tjnzau-20260211181453 -n ns-ptjas check backup status  `kbcli cluster list-backups hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE SOURCE-CLUSTER METHOD STATUS TOTAL-SIZE DURATION DELETION-POLICY CREATE-TIME COMPLETION-TIME EXPIRATION backup-ns-ptjas-hadoop-tjnzau-20260211181453 ns-ptjas hadoop-tjnzau full-namenode Running Delete Feb 11,2026 18:14 UTC+0800 get backup name BACKUP_NAME:backup-ns-ptjas-hadoop-tjnzau-20260211181453 backup_status:hadoop-tjnzau-full-namenode-Running(B backup_status:hadoop-tjnzau-full-namenode-Running(B check backup status done(B backup_status:backup-ns-ptjas-hadoop-tjnzau-20260211181453 ns-ptjas hadoop-tjnzau full-namenode Completed 114152 13s Delete Feb 11,2026 18:14 UTC+0800 Feb 11,2026 18:15 UTC+0800 (B apiVersion: operations.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: hadoop-tjnzau-horizontalscaling- labels: app.kubernetes.io/instance: hadoop-tjnzau app.kubernetes.io/managed-by: kubeblocks namespace: ns-ptjas spec: type: HorizontalScaling clusterName: hadoop-tjnzau force: true horizontalScaling: - componentName: namenode scaleOut: replicaChanges: 2 fromBackup: name: backup-ns-ptjas-hadoop-tjnzau-20260211181453 check cluster status before ops check cluster status done(B cluster_status:Running(B  `kubectl create -f test_ops_cluster_hadoop-tjnzau.yaml`(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-horizontalscaling-jw94t created create test_ops_cluster_hadoop-tjnzau.yaml Success(B  `rm -rf test_ops_cluster_hadoop-tjnzau.yaml`(B  check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME backup-ns-ptjas-hadoop-tjnzau-20260211181453 ns-ptjas Backup hadoop-tjnzau Succeed -/- Feb 11,2026 18:14 UTC+0800 hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Running Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:13 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:13 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:12 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:23Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:12 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:12 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1;standby(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME backup-ns-ptjas-hadoop-tjnzau-20260211181453 ns-ptjas Backup hadoop-tjnzau Succeed -/- Feb 11,2026 18:14 UTC+0800 hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:15 UTC+0800 (B check ops status done(B ops_status:hadoop-tjnzau-horizontalscaling-jw94t ns-ptjas HorizontalScaling hadoop-tjnzau namenode Succeed 2/2 Feb 11,2026 18:15 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-horizontalscaling-jw94t --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-horizontalscaling-jw94t patched  `kbcli cluster delete-ops --name hadoop-tjnzau-horizontalscaling-jw94t --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-jw94t deleted cluster delete backup  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge backups backup-ns-ptjas-hadoop-tjnzau-20260211181453 --namespace ns-ptjas `(B  backup.dataprotection.kubeblocks.io/backup-ns-ptjas-hadoop-tjnzau-20260211181453 patched  `kbcli cluster delete-backup hadoop-tjnzau --name backup-ns-ptjas-hadoop-tjnzau-20260211181453 --force --auto-approve --namespace ns-ptjas `(B  Backup backup-ns-ptjas-hadoop-tjnzau-20260211181453 deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-1 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B cluster namenode scale-in cluster namenode scale-in replicas: 3 check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster scale-in hadoop-tjnzau --auto-approve --force=true --components namenode --replicas 2 --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-kqtpp created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-horizontalscaling-kqtpp -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-kqtpp ns-ptjas HorizontalScaling hadoop-tjnzau namenode Running 0/2 Feb 11,2026 18:17 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:13 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:13 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:12 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:17 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:23Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:17 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 500m / 500m 3Gi / 3Gi nodemanager:21Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:12 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 500m / 500m 3Gi / 3Gi resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-1;standby(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-0 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-horizontalscaling-kqtpp ns-ptjas HorizontalScaling hadoop-tjnzau namenode Succeed 2/2 Feb 11,2026 18:17 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-horizontalscaling-kqtpp ns-ptjas HorizontalScaling hadoop-tjnzau namenode Succeed 2/2 Feb 11,2026 18:17 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-horizontalscaling-kqtpp --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-horizontalscaling-kqtpp patched  `kbcli cluster delete-ops --name hadoop-tjnzau-horizontalscaling-kqtpp --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-horizontalscaling-kqtpp deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-1 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B check component resourcemanager exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=resourcemanager --namespace ns-ptjas | (grep "resourcemanager" || true )`(B  check component nodemanager exists  `kubectl get components -l app.kubernetes.io/instance=hadoop-tjnzau,apps.kubeblocks.io/component-name=nodemanager --namespace ns-ptjas | (grep "nodemanager" || true )`(B  check cluster status before ops check cluster status done(B cluster_status:Running(B  `kbcli cluster vscale hadoop-tjnzau --auto-approve --force=true --components resourcemanager,nodemanager --cpu 600m --memory 3.1Gi --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-verticalscaling-vkwsm created successfully, you can view the progress: kbcli cluster describe-ops hadoop-tjnzau-verticalscaling-vkwsm -n ns-ptjas check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-verticalscaling-vkwsm ns-ptjas VerticalScaling hadoop-tjnzau resourcemanager,nodemanager Running 0/3 Feb 11,2026 18:18 UTC+0800 check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop Delete Updating Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B cluster_status:Updating(B check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:13 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:13 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:12 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:17 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:23Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:17 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 600m / 600m 3328599654400m / 3328599654400m nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:18 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 600m / 600m 3328599654400m / 3328599654400m resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:18 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 600m / 600m 3328599654400m / 3328599654400m resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:19 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 check ops status  `kbcli cluster list-ops hadoop-tjnzau --status all --namespace ns-ptjas `(B  NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME hadoop-tjnzau-verticalscaling-vkwsm ns-ptjas VerticalScaling hadoop-tjnzau resourcemanager,nodemanager Succeed 3/3 Feb 11,2026 18:18 UTC+0800 check ops status done(B ops_status:hadoop-tjnzau-verticalscaling-vkwsm ns-ptjas VerticalScaling hadoop-tjnzau resourcemanager,nodemanager Succeed 3/3 Feb 11,2026 18:18 UTC+0800 (B  `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations hadoop-tjnzau-verticalscaling-vkwsm --namespace ns-ptjas `(B  opsrequest.operations.kubeblocks.io/hadoop-tjnzau-verticalscaling-vkwsm patched  `kbcli cluster delete-ops --name hadoop-tjnzau-verticalscaling-vkwsm --force --auto-approve --namespace ns-ptjas `(B  OpsRequest hadoop-tjnzau-verticalscaling-vkwsm deleted check db_client batch data count  `echo "/opt/hadoop/bin/hdfs dfs -fs hdfs://hadoop-tjnzau-namenode.ns-ptjas.svc.cluster.local:8020 -ls /executions_loop/executions_loop_table/data_*.txt | wc -l" | kubectl exec -it hadoop-tjnzau-namenode-1 --namespace ns-ptjas -- bash`(B  check db_client batch [1661] equal [1661] data Success(B cluster update terminationPolicy WipeOut  `kbcli cluster update hadoop-tjnzau --termination-policy=WipeOut --namespace ns-ptjas `(B  cluster.apps.kubeblocks.io/hadoop-tjnzau updated check cluster status  `kbcli cluster list hadoop-tjnzau --show-labels --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS hadoop-tjnzau ns-ptjas hadoop WipeOut Running Feb 11,2026 16:56 UTC+0800 app.kubernetes.io/instance=hadoop-tjnzau,clusterdefinition.kubeblocks.io/name=hadoop check cluster status done(B cluster_status:Running(B check pod status  `kbcli cluster list-instances hadoop-tjnzau --namespace ns-ptjas `(B  NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME hadoop-tjnzau-datanode-0 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:13 UTC+0800 hadoop-tjnzau-datanode-1 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:13 UTC+0800 hadoop-tjnzau-datanode-2 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:12 UTC+0800 hadoop-tjnzau-datanode-3 ns-ptjas hadoop-tjnzau datanode Running 0 500m / 500m 1Gi / 1Gi data:34Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:17 UTC+0800 hadoop-tjnzau-journalnode-0 ns-ptjas hadoop-tjnzau journalnode Running 0 500m / 500m 1Gi / 1Gi edits-dir:23Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-namenode-0 ns-ptjas hadoop-tjnzau namenode Running standby 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:17 UTC+0800 hadoop-tjnzau-namenode-1 ns-ptjas hadoop-tjnzau namenode Running active 0 500m / 500m 1Gi / 1Gi metadata-dir:25Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:11 UTC+0800 hadoop-tjnzau-nodemanager-0 ns-ptjas hadoop-tjnzau nodemanager Running 0 600m / 600m 3328599654400m / 3328599654400m nodemanager:21Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:18 UTC+0800 hadoop-tjnzau-resourcemanager-0 ns-ptjas hadoop-tjnzau resourcemanager Running active 0 600m / 600m 3328599654400m / 3328599654400m resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000001/10.224.0.8 Feb 11,2026 18:18 UTC+0800 hadoop-tjnzau-resourcemanager-1 ns-ptjas hadoop-tjnzau resourcemanager Running standby 0 600m / 600m 3328599654400m / 3328599654400m resourcemanager:22Gi aks-cicdamdpool-24830451-vmss000002/10.224.0.7 Feb 11,2026 18:19 UTC+0800 hadoop-tjnzau-zookeeper-0 ns-ptjas hadoop-tjnzau zookeeper Running leader 0 500m / 500m 1Gi / 1Gi data:20Gi aks-cicdamdpool-24830451-vmss000004/10.224.0.6 Feb 11,2026 18:11 UTC+0800 snapshot-log:20Gi check pod status done(B check cluster role check cluster role done(B active(B: hadoop-tjnzau-namenode-1 hadoop-tjnzau-resourcemanager-0;standby(B: hadoop-tjnzau-namenode-0 hadoop-tjnzau-resourcemanager-1 connect unsupported engine type: hadoop hadoop-hdfs-datanode-1.0.2 cluster list-logs  `kbcli cluster list-logs hadoop-tjnzau --namespace ns-ptjas `(B  cluster logs  `kbcli cluster logs hadoop-tjnzau --tail 30 --namespace ns-ptjas `(B  2026-02-11 10:19:02,734 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.ZooKeeperServer@1710] - got auth packet /10.244.3.229:59226 2026-02-11 10:19:02,735 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.ZooKeeperServer@1728] - Session 0x5152fa0010: auth success for scheme digest and address /10.244.3.229:59226 2026-02-11 10:19:04,828 [myid:] - INFO [CommitProcessor:0:o.a.z.s.q.LeaderSessionTracker@104] - Committing global session 0x5152fa0011 2026-02-11 10:19:07,954 [myid:] - INFO [NIOWorkerThread-1:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:46916 2026-02-11 10:19:07,954 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:46930 2026-02-11 10:19:12,655 [myid:] - INFO [RequestThrottler:o.a.z.s.q.QuorumZooKeeperServer@156] - Submitting global closeSession request for session 0x5152fa0003 2026-02-11 10:19:12,846 [myid:] - INFO [RequestThrottler:o.a.z.s.q.QuorumZooKeeperServer@156] - Submitting global closeSession request for session 0x5152fa0002 2026-02-11 10:19:17,954 [myid:] - INFO [NIOWorkerThread-1:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:58080 2026-02-11 10:19:17,955 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:58092 2026-02-11 10:19:27,954 [myid:] - INFO [NIOWorkerThread-1:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:60664 2026-02-11 10:19:27,955 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:60676 2026-02-11 10:19:37,954 [myid:] - INFO [NIOWorkerThread-1:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:53560 2026-02-11 10:19:37,955 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:53572 2026-02-11 10:19:40,549 [myid:] - INFO [NIOWorkerThread-1:o.a.z.s.NIOServerCnxn@532] - Processing srvr command from /127.0.0.1:60036 2026-02-11 10:19:47,955 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:47778 2026-02-11 10:19:47,956 [myid:] - INFO [NIOWorkerThread-1:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:47788 2026-02-11 10:19:52,374 [myid:] - INFO [CommitProcessor:0:o.a.z.s.q.LeaderSessionTracker@104] - Committing global session 0x5152fa0012 2026-02-11 10:19:52,455 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.ZooKeeperServer@1710] - got auth packet /10.244.2.220:55506 2026-02-11 10:19:52,455 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.ZooKeeperServer@1728] - Session 0x5152fa0012: auth success for scheme digest and address /10.244.2.220:55506 2026-02-11 10:19:52,457 [myid:] - INFO [NIOWorkerThread-1:o.a.z.s.ZooKeeperServer@1710] - got auth packet /10.244.2.220:55506 2026-02-11 10:19:52,458 [myid:] - INFO [NIOWorkerThread-1:o.a.z.s.ZooKeeperServer@1728] - Session 0x5152fa0012: auth success for scheme digest and address /10.244.2.220:55506 2026-02-11 10:19:54,492 [myid:] - INFO [CommitProcessor:0:o.a.z.s.q.LeaderSessionTracker@104] - Committing global session 0x5152fa0013 2026-02-11 10:19:57,953 [myid:] - INFO [NIOWorkerThread-1:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:34216 2026-02-11 10:19:57,954 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:34228 2026-02-11 10:20:07,955 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:43668 2026-02-11 10:20:07,955 [myid:] - INFO [NIOWorkerThread-1:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:43674 2026-02-11 10:20:17,954 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:52780 2026-02-11 10:20:17,954 [myid:] - INFO [NIOWorkerThread-1:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:52786 2026-02-11 10:20:27,956 [myid:] - INFO [NIOWorkerThread-1:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:43772 2026-02-11 10:20:27,956 [myid:] - INFO [NIOWorkerThread-2:o.a.z.s.NIOServerCnxn@532] - Processing ruok command from /0:0:0:0:0:0:0:1:43770 delete cluster hadoop-tjnzau  `kbcli cluster delete hadoop-tjnzau --auto-approve --namespace ns-ptjas `(B  configmap "hadoop-tjnzau-namenode-hosts" deleted Cluster hadoop-tjnzau deleted pod_info:hadoop-tjnzau-datanode-0 2/2 Running 0 6m56s hadoop-tjnzau-datanode-1 2/2 Running 0 7m23s hadoop-tjnzau-datanode-2 2/2 Running 0 8m25s hadoop-tjnzau-datanode-3 2/2 Running 0 3m22s hadoop-tjnzau-journalnode-0 1/1 Running 0 8m56s hadoop-tjnzau-namenode-0 2/2 Running 0 3m22s hadoop-tjnzau-namenode-1 2/2 Running 1 (8m31s ago) 8m55s hadoop-tjnzau-nodemanager-0 1/1 Running 0 2m11s hadoop-tjnzau-resourcemanager-0 2/2 Running 0 2m10s hadoop-tjnzau-resourcemanager-1 2/2 Running 0 75s hadoop-tjnzau-zookeeper-0 2/2 Running 0 8m55s delete cluster pod done(B check cluster resource non-exist OK: pvc(B delete cluster done(B Hadoop Test Suite All Done!(B Test Engine: hadoop Test Type: 68 --------------------------------------Hadoop (Topology = ha-cluster Replicas 2) Test Result-------------------------------------- [PASSED]|[Create]|[Topology=ha-cluster;ComponentDefinition=hadoop-hdfs-datanode-1.0.2;ComponentVersion=hadoop;ServiceVersion=3.3.1;]|[Description=Create a cluster with the specified topology ha-cluster with the specified component definition hadoop-hdfs-datanode-1.0.2 and component version hadoop and service version 3.3.1](B [SKIPPED]|[VerticalScaling]|[ComponentName=namenode,datanode,journalnod]|[Description=VerticalScaling the cluster specify component namenode,datanode,journalnod](B [PASSED]|[VolumeExpansion]|[ComponentName=namenode;ComponentVolume=metadata-dir]|[Description=VolumeExpansion the cluster specify component namenode and volume metadata-dir](B [PASSED]|[HorizontalScaling Out]|[ComponentName=nodemanager]|[Description=HorizontalScaling Out the cluster specify component nodemanager](B [PASSED]|[HorizontalScaling In]|[ComponentName=nodemanager]|[Description=HorizontalScaling In the cluster specify component nodemanager](B [PASSED]|[VolumeExpansion]|[ComponentName=resourcemanager;ComponentVolume=resourcemanager]|[Description=VolumeExpansion the cluster specify component resourcemanager and volume resourcemanager](B [PASSED]|[VolumeExpansion]|[ComponentName=nodemanager;ComponentVolume=nodemanager]|[Description=VolumeExpansion the cluster specify component nodemanager and volume nodemanager](B [PASSED]|[Stop]|[-]|[Description=Stop the cluster](B [PASSED]|[Start]|[-]|[Description=Start the cluster](B [PASSED]|[HorizontalScaling Out]|[ComponentName=datanode]|[Description=HorizontalScaling Out the cluster specify component datanode](B [PASSED]|[Restart]|[ComponentName=namenode,datanode]|[Description=Restart the cluster specify component namenode,datanode](B [PASSED]|[Restart]|[ComponentName=resourcemanager,nodemanager]|[Description=Restart the cluster specify component resourcemanager,nodemanager](B [PASSED]|[VolumeExpansion]|[ComponentName=journalnode;ComponentVolume=data]|[Description=VolumeExpansion the cluster specify component journalnode and volume data](B [PASSED]|[HorizontalScaling Out]|[ComponentName=resourcemanager]|[Description=HorizontalScaling Out the cluster specify component resourcemanager](B [PASSED]|[HorizontalScaling In]|[ComponentName=resourcemanager]|[Description=HorizontalScaling In the cluster specify component resourcemanager](B [PASSED]|[VolumeExpansion]|[ComponentName=datanode;ComponentVolume=data]|[Description=VolumeExpansion the cluster specify component datanode and volume data](B [PASSED]|[Backup]|[BackupMethod=full-journalnode]|[Description=The cluster full-journalnode Backup](B [PASSED]|[HorizontalScaling Out]|[ComponentName=journalnode]|[Description=HorizontalScaling Out the cluster specify component journalnode](B [PASSED]|[HorizontalScaling In]|[ComponentName=journalnode]|[Description=HorizontalScaling In the cluster specify component journalnode](B [SKIPPED]|[Restart]|[ComponentName=zookeeper,journalnod]|[Description=Restart the cluster specify component zookeeper,journalnod](B [PASSED]|[Restart]|[-]|[Description=Restart the cluster](B [PASSED]|[Backup]|[BackupMethod=full-namenode]|[Description=The cluster full-namenode Backup](B [PASSED]|[HorizontalScaling Out]|[ComponentName=namenode]|[Description=HorizontalScaling Out the cluster specify component namenode](B [PASSED]|[HorizontalScaling In]|[ComponentName=namenode]|[Description=HorizontalScaling In the cluster specify component namenode](B [PASSED]|[VerticalScaling]|[ComponentName=resourcemanager,nodemanager]|[Description=VerticalScaling the cluster specify component resourcemanager,nodemanager](B [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut](B [PASSED]|[Delete]|[-]|[Description=Delete the cluster](B [END]