Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]bench pods of apecloud-mysql cluster are not in running status #8801

Closed
tianyue86 opened this issue Jan 14, 2025 · 2 comments
Closed

[BUG]bench pods of apecloud-mysql cluster are not in running status #8801

tianyue86 opened this issue Jan 14, 2025 · 2 comments
Assignees
Labels
kind/bug Something isn't working severity/major Great chance user will encounter the same problem
Milestone

Comments

@tianyue86
Copy link

Describe the env
Kubernetes: v1.31.1-aliyun.1
KubeBlocks: 1.0.0-beta.22
kbcli: 1.0.0-beta.9

To Reproduce
Steps to reproduce the behavior:

  1. Create apecloud-mysql cluster with yaml below
apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
  name: smarte-objvxk
  namespace: default
  labels: 
    app.kubernetes.io/instance: smarte-objvxk
spec:
  clusterDef: apecloud-mysql
  topology: apecloud-mysql
  terminationPolicy: WipeOut
  componentSpecs:
    - name: mysql
      serviceVersion: 8.0.30
      disableExporter: true
      replicas: 3
      resources:
        requests:
          cpu: 500m
          memory: 1Gi
        limits:
          cpu: 500m
          memory: 1Gi
      volumeClaimTemplates:
        - name: data
          spec:
            storageClassName:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 20Gi
  1. Add bench pod
apiVersion: v1
kind: Pod
metadata:
  name: test-sysbench-smarte-objvxk-leader
  namespace: default
spec:
  containers:
    - name: test-sysbench
      image: apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/customsuites:latest
      env:
        - name: TYPE
          value: "2"
        - name: FLAG
          value: "3"
        - name: CONFIGS
          value: "mode:all,host:smarte-objvxk-mysql-2.smarte-objvxk-mysql-headless.default.svc,user:root,password:8Yk686EPP79dse33,port:3306,db:benchtest,threads:10,times:30,insert_thread_num:3,update_thread_num:3,sst_file_limit:2000,padding_size:128,mysql_storage_engine:smartengine,type:scan_check_mixed.lua"

  restartPolicy: Never

-------------------------
apiVersion: v1
kind: Pod
metadata:
  name: test-sysbench-smarte-objvxk-follower
  namespace: default
spec:
  containers:
    - name: test-sysbench
      image: apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/customsuites:latest
      env:
        - name: TYPE
          value: "2"
        - name: FLAG
          value: "3"
        - name: CONFIGS
          value: "mode:run,host:smarte-objvxk-mysql-0.smarte-objvxk-mysql-headless.default.svc,user:root,password:8Yk686EPP79dse33,port:3306,db:benchtest,threads:10,times:20,insert_thread_num:0,update_thread_num:0,sst_file_limit:2000,padding_size:128,mysql_storage_engine:smartengine,type:scan_check_mixed.lua"
  1. check pod status
k get pod|grep smart
smarte-objvxk-mysql-0                  4/4     Running            0                97m
smarte-objvxk-mysql-1                  4/4     Running            0                96m
smarte-objvxk-mysql-2                  4/4     Running            0                96m
test-sysbench-smarte-objvxk-follower   0/1     CrashLoopBackOff   18 (54s ago)     68m
test-sysbench-smarte-objvxk-leader     0/1     Error              0                78m
  1. describe pod
k describe pod test-sysbench-smarte-objvxk-follower
Events:
  Type     Reason          Age                     From               Message
  ----     ------          ----                    ----               -------
  Normal   Scheduled       8m32s                   default-scheduler  Successfully assigned default/test-sysbench-smarte-objvxk-follower to cn-zhangjiakou.10.0.0.144
  Normal   AllocIPSucceed  8m32s                   terway-daemon      Alloc IP 10.0.0.190/24 took 30.55256ms
  Normal   Pulled          8m31s                   kubelet            Successfully pulled image "apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/customsuites:latest" in 106ms (106ms including waiting). Image size: 565147756 bytes.
  Normal   Pulled          8m30s                   kubelet            Successfully pulled image "apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/customsuites:latest" in 100ms (100ms including waiting). Image size: 565147756 bytes.
  Normal   Pulled          8m13s                   kubelet            Successfully pulled image "apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/customsuites:latest" in 96ms (96ms including waiting). Image size: 565147756 bytes.
  Normal   Created         7m44s (x4 over 8m31s)   kubelet            Created container test-sysbench
  Normal   Started         7m44s (x4 over 8m31s)   kubelet            Started container test-sysbench
  Normal   Pulled          7m44s                   kubelet            Successfully pulled image "apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/customsuites:latest" in 76ms (76ms including waiting). Image size: 565147756 bytes.
  Normal   Pulling         6m53s (x5 over 8m32s)   kubelet            Pulling image "apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/customsuites:latest"
  Warning  BackOff         3m23s (x25 over 8m28s)  kubelet            Back-off restarting failed container test-sysbench in pod test-sysbench-smarte-objvxk-follower_default(0a5c1abe-0d45-42ff-953c-a3b7184f773e)
  1. logs
    benchlogs.txt

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@tianyue86 tianyue86 added the kind/bug Something isn't working label Jan 14, 2025
@tianyue86 tianyue86 added the severity/major Great chance user will encounter the same problem label Jan 17, 2025
@tianyue86 tianyue86 added this to the Release 1.0.0 milestone Jan 17, 2025
@tianyue86
Copy link
Author

@fengluodb please take a look at this bench related issue, thanks!

@JashBook
Copy link
Collaborator

JashBook commented Jan 20, 2025

This is a bench test for smartengine. If enable smartengine fails, this case will also fail.
dup #8827

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working severity/major Great chance user will encounter the same problem
Projects
None yet
Development

No branches or pull requests

5 participants