Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-2352

Sudden memory leak leading to OOM kill

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 2.2.18, 2.3.4
    • N/A
    • N/A
    • 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.

      Attachments

        Activity

          People

            markus makela markus makela
            hholzgra Hartmut Holzgraefe
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.