[MXS-2224] MaxScale 2.3.2 Memory leaks causes OOM Created: 2018-12-18 Updated: 2018-12-22 Resolved: 2018-12-22 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | 2.3.2 |
| Fix Version/s: | 2.2.18, 2.3.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Snow | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Debian 8, Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) x86_64 GNU/Linux |
||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Hello! We've tried to upgrade MaxScale to the 2.3.2 from 2.1.17, unfortunately, the story from the issue https://jira.mariadb.org/browse/MXS-1977 remains despite of fix Profile of memory consumption the same as in mxs-1977 - gradual growth, config is following:
And last messages in log before crash:
|
| Comments |
| Comment by Johan Wikman [ 2018-12-18 ] |
|
Could you please try 2.2.18 There were some leaks in 2.2.17 that were addressed in 2.2.18. Those fixes are not in 2.3.2, but will be in 2.3.3 that is likely to be released first thing after new year. |
| Comment by Daniel Snow [ 2018-12-20 ] |
|
Hi Johan! Thank you for your advice, 2.2.18 works good for our workload with no memory leaking. BTW it's strange codeflow to not to include old fixes into the new releases. Haven't ever seen MCAAHNY! |
| Comment by Johan Wikman [ 2018-12-21 ] |
|
That's good! |
| Comment by markus makela [ 2018-12-22 ] |
|
Fixed in 2.2.18 and will be a part of 2.3.3. |