[MXS-2872] Maxscale consume memory and growing upto 10GB Created: 2020-02-04  Updated: 2020-02-04  Resolved: 2020-02-04

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: 2.2.20
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Manokaran Assignee: Johan Wikman
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

Maxscale Total memory consumption is increasing upto 10.7 GB,

In this physical memory itself consuming close to 700 MB and Swap using remaining.

Swap memory usage didn't come down ,and not releasing it.

1. Why maxscale is using 10GB of memory even we are using only for proxy purpose?
2. Is there any parameter has to be defined to control memory consumption ?
3. Why memory used by maxscale is not getting released?



 Comments   
Comment by Johan Wikman [ 2020-02-04 ]

If you have enabled the session command history, that may be a reason although not that likely as the memory usage is rather extreme. If there is a substantial difference in speed between the client < - > maxscale network and the maxscale < - > servers network, then you may be experiencing an effect that https://mariadb.com/kb/en/mariadb-maxscale-24-mariadb-maxscale-configuration-guide/#writeq_high_water and https://mariadb.com/kb/en/mariadb-maxscale-24-mariadb-maxscale-configuration-guide/#writeq_low_water would fix.

Comment by Johan Wikman [ 2020-02-04 ]

MaxScale 2.2 has reached its EOL. Please upgrade to a newer version.

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