Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.1.1
-
None
Description
Hello,
I've experienced behavior which points to the memory leak in MaxScale 1.1.1.
How to repeat:
Decompress attached tarball, download and install pt-log-player from Percona Toolkit 2.1.11
Open a screen with two sessions.
In the first session run:
while true ; do ps auxf | grep pt-log-player | awk '
' | xargs kill -9 ; sleep 4s ; done
In the second session run:
while true ; do /root/percona-toolkit-2.1.11/bin/pt-log-player --play ./sessions --base-dir ./results h=your_IP,P=your_RWsplit_port,u=youruser,p=yourpass ; done
After a while observe memory utilization growing:
root@ip-10-10-92-43:~/massif# ps auxf | grep maxscale
root 14056 0.6 48.3 2554104 1955360 ? Ssl 13:37 0:14 /usr/local/mariadb-maxscale/bin/maxscale
Session files contain:
root@ip-10-10-90-60:~/maxscale_debug# cat ./sessions/sessions-* | sort | uniq -c
488571 SET AUTOCOMMIT=0
486362 SET AUTOCOMMIT=1
1973024 SET NAMES utf8
MaxScale version:
root@ip-10-10-92-43:~/massif# /usr/local/mariadb-maxscale/bin/maxscale --version
1.1.1
I've attached tarball with session files and massif report. For this test I've used single PXC instance in a readwritesplit router. readconnroute doesn't seem to be affected.
Attachments
Issue Links
- includes
-
MXS-266 pt-log-player fails with readwritesplit
- Closed