[MXS-2352] Sudden memory leak leading to OOM kill Created: 2019-02-25 Updated: 2019-09-05 Resolved: 2019-09-05 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | 2.2.18, 2.3.4 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Hartmut Holzgraefe | Assignee: | markus makela |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Linux |
||
| Sprint: | MXS-SPRINT-77, MXS-SPRINT-78 |
| Description |
|
Maxscale used up almost all the machines memory, and was killed by the kernels OOM kill mechanism. Machines memory and swap utilization was monitored with "sar" every10 minutes, but did not show any excessive memory or swap use, so the maxscale process must have grown beyond all limits quickly, and not gradually over time. |
| Comments |
| Comment by markus makela [ 2019-04-01 ] |
|
Could be related to |
| Comment by markus makela [ 2019-04-03 ] |
|
Could be related to either |
| Comment by markus makela [ 2019-04-29 ] |
|
Does this happen on 2.3? |
| Comment by Hartmut Holzgraefe [ 2019-05-16 ] |
|
Still seen with Maxscale 2.3.4 |