Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Not a Bug
-
2.4.8
-
Debian Buster
Description
Hi,
few days ago we upgraded from MaxScale 2.4.x to latest 2.4.8 and also from "readconnroute" to "readwritesplit".
I attached our maxscale.cnf and chart where is visible RSS RAM of MaxScale. After each midnight RSS increased dozens of MB. 3 days ago i restarted MaxScale - this is reason why memory was so low/cleared.
We have this maxscale.cnf on multiple servers/clients with MaxScale 2.4.8 and all of them have this memory leak.
I can provide you result of any maxctrl/other command, which can help you.
UPDATE: i attached still one screenshot from another project/server with same maxscale.conf. We imported one database from another server (148 InnoDB tables, approx. 18 million records and 1.5 GB of data in total). MaxScale memory increased from ~85 MB to ~388 MB. Maybe it's based on same reason, maybe not.
Thank you.