[MXS-2908] Memory leak in 2.3.16? Created: 2020-03-02 Updated: 2020-07-04 Resolved: 2020-07-04 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | 2.3.16, 2.4.8 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Hartmut Holzgraefe | Assignee: | markus makela |
| Resolution: | Cannot Reproduce | Votes: | 1 |
| Labels: | need_feedback | ||
| Attachments: |
mem1.png
mem2.png
|
||||||||
| Issue Links: |
|
||||||||
| Sprint: | MXS-SPRINT-104, MXS-SPRINT-105 | ||||||||
| Description |
|
Memory usage of a maxscale instance stayed low for a little less than 24 hours, then went up to about 4GB quickly within a span of ~30 minutes: mem1.png shows the memory useage over a full after start, mem2.png the incline over the critical 30min period (note: x axis is in minutes, and y axis in kilobytes, don't let that confuse you) This was originally reported against 2.3.9, which had some known leaks, but still seems to happen after upgrade to 2.3.16 (graphs are from 2.3.9) |
| Comments |
| Comment by markus makela [ 2020-03-09 ] |
|
Found a memory leak in the maxctrl list commands and maxctrl call command code. |
| Comment by markus makela [ 2020-03-30 ] |
|
Need feedback on whether the latest releases fix it. |
| Comment by markus makela [ 2020-07-03 ] |
|
Enabling writeq_high_water=16Mi and writeq_low_water=8Ki might solve it. |