[MXS-4055] Maxscale used a lot of RAM | Out of memory: Kill process Maxscale Created: 2022-03-23  Updated: 2022-04-26  Resolved: 2022-04-07

Status: Closed
Project: MariaDB MaxScale
Component/s: maxbase
Affects Version/s: 6.2.1, 6.2.3
Fix Version/s: 6.2.3

Type: Bug Priority: Critical
Reporter: Pon Suresh Pandian (Inactive) Assignee: Niclas Antti
Resolution: Not a Bug Votes: 1
Labels: maxscale
Environment:

Debian OS

Attachments: PNG File Bildschirmfoto 2022-03-18 um 17.01.09.png     PNG File Bildschirmfoto 2022-03-22 um 07.01.38.png     PNG File Bildschirmfoto 2022-03-22 um 07.01.49.png    
Sprint: 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..

 Comments   
Comment by Niclas Antti [ 2022-04-07 ]

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).

Generated at Thu Feb 08 04:25:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.