[MXS-4100] connection_keepalive=0 causes a memory leak Created: 2022-04-19 Updated: 2022-06-06 Resolved: 2022-06-06 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Protocol |
| Affects Version/s: | 2.5.20, 6.3.1 |
| Fix Version/s: | 2.5.21, 6.4.0 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Oleg | Assignee: | Niclas Antti |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | None | ||
| Environment: |
Ubuntu 20.04.4 LTS (GNU/Linux 5.4.0-107-generic x86_64) |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
Under heavy load, MaxScale consumes RAM indefinitely. Tested from 2.5.19 to 6.3.0. sysbench /usr/share/sysbench/oltp_read_write.lua --mysql-host=1.1.1.1 --mysql-port=33306 --mysql-user=testuser --mysql-password='testpass' --mysql-db=sbtest --db-driver=mysql --tables=3 --table-size=10000000 --report-interval=10 --threads=400 --time=8000 --db-ps-mode=disable run On another server with a lot of RAM, I saw 150GB of memory used by the maxscale process in 8 hours of sysbench
|
| Comments |
| Comment by Oleg [ 2022-04-19 ] |
|
Hmm... I just found the reason was in "connection_keepalive=0s" in the service sections. |
| Comment by markus makela [ 2022-04-19 ] |
|
dzoleg so removing connection_keepalive=0s from the configuration fixes it? |
| Comment by Oleg [ 2022-04-19 ] |
|
Yes, fixed it. Removing or setting any values except 0s fixes the issue. |
| Comment by markus makela [ 2022-04-19 ] |
|
Does this happen if you use the readwritesplit router? |
| Comment by Oleg [ 2022-04-19 ] |
|
This happen on readconnroute router. I don't tested this with other routers, because I need only readconnroute. |
| Comment by markus makela [ 2022-04-19 ] |
|
If you can test this with readwritesplit, it would tell us whether the problem is only related to the readconnroute or if it's something else. |
| Comment by Oleg [ 2022-04-19 ] |
|
Looks like no problem with readwritesplit. |