Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
2.2.18, 2.3.4
-
None
-
Linux
-
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.