# Infinite database initialization on creation **URL:** \ **Category:** Percona Everest\ **Created:** [January 19, 2024, 1:45pm UTC](https://forums.percona.com/t/infinite-database-initialization-on-creation/27887 "2024-01-19T13:45:58Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\ **Post date:** [January 19, 2024, 1:45pm UTC](https://forums.percona.com/t/infinite-database-initialization-on-creation/27887/1 "2024-01-19T13:45:58Z")
Hi, I’m experimenting with Percona Everest and ran into a problem. I have created several databases for my experiments. When I started to create the next database, it didn’t get created, for several hours now the database is in Initialization status. Please advise what I need to do and how to identify the problem. ![Screenshot 2024-01-19 at 5.43.14 PM](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/3/35fbff1b92ff0855f10aaa2d8ca65292526686f9.png) ---
**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\ **Post date:** [January 22, 2024, 2:59pm UTC](https://forums.percona.com/t/infinite-database-initialization-on-creation/27887/2 "2024-01-22T14:59:15Z")
I checked the pods running ```auto kubectl -n percona-everest get pods ``` It turned out that I had run out of cluster resources, because the pxc pods were also running haproxy pods, for which I had not calculated the resources. ---
**Author:** ![Athar\_Mahboob](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/athar_mahboob/32/16841_2.png) [@Athar\_Mahboob](https://forums.percona.com/u/Athar_Mahboob)\ **Post date:** [June 10, 2024, 1:21pm UTC](https://forums.percona.com/t/infinite-database-initialization-on-creation/27887/3 "2024-06-10T13:21:09Z")
I am having the same problem with latest release of Percona Everest 0.10.1. The cluster is set up using minikube with 3 nodes, 6 cpu cores and 16GB RAM. I am able to create mongodb database. Cluster resources use remains moderate: $ kubectl top nodes NAME CPU(cores) CPU% MEMORY(bytes) MEMORY% ha3 604m 5% 1889Mi 5% ha3-m02 665m 5% 1772Mi 5% ha3-m03 614m 5% 2485Mi 7% When mysql database is created it remains in initializing with portainer monitoring showing almost infinite memory reservation. When mysql database is not in creation / initialization process: Memory reservation 19989 / 99801 MB - 20% However when mysql database instance is created: Memory reservation reaches astronomical value: Memory reservation 5186173034815 / 99801 MB - 5196514098% It appears haproxy pod keeps restarting and is unable to complete what it is supposed to do to make the database cluster functional. Any help would be appreciated. ---
**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\ **Post date:** [June 10, 2024, 1:25pm UTC](https://forums.percona.com/t/infinite-database-initialization-on-creation/27887/4 "2024-06-10T13:25:19Z")
Do you happen to have a MacBook with an ARM (M1,2,3) processor? ---
**Author:** ![Athar\_Mahboob](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/athar_mahboob/32/16841_2.png) [@Athar\_Mahboob](https://forums.percona.com/u/Athar_Mahboob)\ **Post date:** [June 10, 2024, 1:34pm UTC](https://forums.percona.com/t/infinite-database-initialization-on-creation/27887/5 "2024-06-10T13:34:49Z")
No. I am working on a Dell XPS 17 with x86-64, 6 Cores, 12 Threads, 32 GB RAM. Kubernetes cluster created with minikube: minikube start -p ha3 --cpus=6 --memory=16384 --nodes=3 --driver=docker --ha=true ---
**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\ **Post date:** [June 10, 2024, 1:39pm UTC](https://forums.percona.com/t/infinite-database-initialization-on-creation/27887/6 "2024-06-10T13:39:36Z")
I’m not an expert, but it seems Minikube with 3 nodes and 6 CPUs requires 3\*6=18 CPUs in the system. I think you need to reduce the number of Minikube nodes to 1. You can also try [Kind](https://kind.sigs.k8s.io/) or k3s Our developers use this too ---
**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\ **Post date:** [June 10, 2024, 1:47pm UTC](https://forums.percona.com/t/infinite-database-initialization-on-creation/27887/7 "2024-06-10T13:47:05Z")
In my case, the problem was the Mac, as the operators don’t support ARM architecture yet. ---
**Author:** ![Athar\_Mahboob](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/athar_mahboob/32/16841_2.png) [@Athar\_Mahboob](https://forums.percona.com/u/Athar_Mahboob)\ **Post date:** [June 10, 2024, 2:56pm UTC](https://forums.percona.com/t/infinite-database-initialization-on-creation/27887/8 "2024-06-10T14:56:12Z")
Ok. It sounds like a reasonable suggestion. For information the output of kubectl describe pod -n dev mysql-eay-pxc-1 on a stuck up pod is: ``` node.kubernetes.io/unreachable:NoExecute op=Exists for 300s ``` Events: Type Reason Age From Message * * * Warning FailedScheduling 5m52s default-scheduler running Bind plugin “DefaultBinder”: Operation cannot be fulfilled on pods/binding “mysql-eay-pxc-1”: pod mysql-eay-pxc-1 is already assigned to node “ha3-m03” Warning FailedScheduling 5m52s default-scheduler running Bind plugin “DefaultBinder”: Operation cannot be fulfilled on pods/binding “mysql-eay-pxc-1”: pod mysql-eay-pxc-1 is already assigned to node “ha3-m03” Normal Scheduled 5m53s default-scheduler Successfully assigned dev/mysql-eay-pxc-1 to ha3-m03 Normal Pulled 5m50s kubelet Successfully pulled image “[docker.io/percona/percona-xtradb-cluster-operator:1.13.0](http://docker.io/percona/percona-xtradb-cluster-operator:1.13.0)” in 2.666s (2.666s including waiting). Image size: 140547877 bytes. Normal Pulled 5m46s kubelet Successfully pulled image “[docker.io/percona/percona-xtradb-cluster-operator:1.13.0](http://docker.io/percona/percona-xtradb-cluster-operator:1.13.0)” in 2.681s (2.681s including waiting). Image size: 140547877 bytes. Normal Pulled 5m29s kubelet Successfully pulled image “[docker.io/percona/percona-xtradb-cluster-operator:1.13.0](http://docker.io/percona/percona-xtradb-cluster-operator:1.13.0)” in 2.657s (2.657s including waiting). Image size: 140547877 bytes. Normal Pulled 4m58s kubelet Successfully pulled image “[docker.io/percona/percona-xtradb-cluster-operator:1.13.0](http://docker.io/percona/percona-xtradb-cluster-operator:1.13.0)” in 2.631s (2.631s including waiting). Image size: 140547877 bytes. Normal Created 4m57s (x4 over 5m50s) kubelet Created container pxc-init Normal Started 4m57s (x4 over 5m49s) kubelet Started container pxc-init Normal Pulling 4m16s (x5 over 5m52s) kubelet Pulling image “[docker.io/percona/percona-xtradb-cluster-operator:1.13.0](http://docker.io/percona/percona-xtradb-cluster-operator:1.13.0)” Normal Pulled 4m13s kubelet Successfully pulled image “[docker.io/percona/percona-xtradb-cluster-operator:1.13.0](http://docker.io/percona/percona-xtradb-cluster-operator:1.13.0)” in 2.946s (2.946s including waiting). Image size: 140547877 bytes. Warning BackOff 49s (x24 over 5m46s) kubelet Back-off restarting failed container pxc-init in pod mysql-eay-pxc-1\_dev(045c88ce-1bc7-46e9-b98c-40cb5f7924bf)