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

XTRADB Pods OOMkilled with limit and without limit the always use 16GB of memory #1819

Open
Elyytscha opened this issue Sep 17, 2024 · 0 comments
Labels

Comments

@Elyytscha
Copy link

Elyytscha commented Sep 17, 2024

Report

cr:

apiVersion: pxc.percona.com/v1
kind: PerconaXtraDBCluster
metadata:
  name: sys-stat-db-cluster
  namespace: database
spec:
  allowUnsafeConfigurations: true
  crVersion: 1.11.0
  enableCRValidationWebhook: true
  haproxy:
    enabled: false
  proxysql:
    enabled: true
    gracePeriod: 30
    image: 'percona/percona-xtradb-cluster-operator:1.11.0-proxysql'
    imagePullPolicy: Always
    podDisruptionBudget:
      maxUnavailable: 1
    size: 3
    volumeSpec:
      persistentVolumeClaim:
        resources:
          requests:
            storage: 1G
  pxc:
    configuration: |
      [mysqld]

      innodb_buffer_pool_size=1G
    image: 'percona/percona-xtradb-cluster:5.7'
    size: 3
    volumeSpec:
      persistentVolumeClaim:
        resources:
          requests:
            storage: 1G
  secretsName: system-status-xtradb-cluster-secrets
  upgradeOptions:
    apply: disabled
    schedule: 0 4 * * *

we already tried the newest version of the operator 1.15, it has the exact same behaviour, it alwas uses 16gb ram, we can not get it to fit a size for a small db, we want that it uses max 2gb ram because its only a test database which definitely does not need 16gb ram x3

when we add

  pxc:
    resources:
      limits:
        memory: 2Gi
      requests:
        memory: 2Gi

it just gets oomkilled because it wants to use again 16gb of memory.

image
image

More about the problem

expected behaviour: no oomkill

Steps to reproduce

  1. use the provided cr and try to set limits

Versions

  1. 1.28.x
  2. 1.11 - 1.15
  3. 5.7.x

Anything else?

No response

@Elyytscha Elyytscha added the bug label Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant