we are facing performance issue when we deploy metabase newer version (v0.45.2) with containerized metabase and mysql database version v5.7.7 also a container on eks cluster and the database is provisioned with persistent volume on aws and metabase running with java version
i dunno why mysql container reaches its memory peak and then crashes and keep doing this stuff also we tried to deploy mysql database as container on eks with the recommended version and another version and its keep doing the same behaviour and here's some cpu and memory utilization from grafana
Do you have any Oracle database configured in your Metabase?
I was facing the same issue with containerized metabase and saw your post yesterday. I was getting a frequent error in the log (Locate not recognized) when this connection was requested. The reason for this was the difference between the timezone in the Metabase and the timezone in the container.
For some reason, when the connection was requested, the error didn't happen immediately and the processes kept running, resulting in many concurrent processess, including sync and scan databases (known as heavy processes).
Modifying the timezone on container solved the issue. Perhaps you can try this approach even if you don't have an Oracle connection.
@Luiggi for database container we're using cpu and memory limits in Kubernetes , the stable version runs with resources as the following :
CPU : 3 cores
memory : 10 GB
however Metabase container not facing and issues with it
but when upgrade to specified version the database container sent to the grave , we tried to scale the resources up and the same behavior happened .