Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Not a Bug
-
6.2.1, 6.2.3
-
Debian OS
-
MXS-SPRINT-154
Description
Hi Team,
Maxscale 6.2.1 & 6.2.3 used a lot of RAM and Maxscale process have been killed due to:
Out of memory: Kill process 51956 (maxscale) score 927 or sacrifice child
The VM has 16 GB RAM and can extra 4 GB swapping.
Here I have attached the memory usage graphs and maxscale config file.
Please check it and let me know if you need any other logs..
This was most likely a case of too little RAM on the MaxScale node. After an upgrade to 32GB the usage seemed to level out at 22GB.
Also, and importantly, MaxScale was upgraded to 6.2.3 to decrease query cache usage (bug in versions before 6.2.3).