Which MYSQL operator should be used?

MySQL & MariaDB Percona Operator for MySQL
1

Hello,

we use currently github .com/percona/percona-xtradb-cluster-operator in production but we have issues:
github .com/percona/percona-xtradb-cluster-operator/issues/1819 we are not able to set limits or size the db to something smaller then 16GB Memory which is really terrible when we just want a small cluster for a testing database (which should behave exactly the same like their brother in production which is bigger sized)

so i think we should take a step back and ask first which is even the correct operator to deploy mysql in production right now with percona operators? because right now i see 3 operators

github .com/percona/percona-server-mysql-operator
github .com/percona/percona-xtradb-cluster-operator
github .com/percona/everest-operator

2

Hi

The github .com/percona/everest-operator is responsible for the Percona Everest application and does not create databases.

I will move your question to the MySQL Operators category, you will get faster help there.

3

Hi @Elytscha_Smith, We will check this task to help you. Do you need to have MySQL 5.7? It is EOL now.

4

yes mysql 5.7 is needed for this specific application, but this happens also with mysql 8.x

5

Any chance you had already time to look into this? XTRADB Pods OOMkilled with limit and without limit the always use 16GB of memory · Issue #1819 · percona/percona-xtradb-cluster-operator · GitHub

just to note, this caused quite some trouble at our company, basically our small onpremise k8s died because the 3 xtradb mysql nodes had eaten 48gb of memory on the cluster for a small database, so the cluster ran oom and that caused other applications outtake.

In my testings (i tested a lot after this) i wasn’t able to create a mysql cluster with the operator which did need less then 16gb ram per node to function, not with 5.x, not with 8.x