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

Serious leak that causes MaxScale to crash

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Not a Bug
    • Affects Version/s: 1.2.1
    • Fix Version/s: 1.2.1
    • Component/s: Core
    • Labels:
      None

      Description

      From https://support.mariadb.com/view.php?id=10125

      "Over the past several weeks we've been doing load testing. What we've noticed is that the amount of memory consume by maxscale is consistently increasing. See attached screenshot. We've more than doubled the amount of RAM on maxscale from 8G to 20G and while it does take longer to use 20G during the endurance testing maxscale does eventually use the RAM and restart the service. This causes error with our application and invalides the load test. I've also noticed that the connection count is staying pretty low. The RAM does not start to climb until load testing has started, IE when there is not connections maxscale RAM stays flat. Can we please escalate this to the maxscale team? We did not see this behavior when we originally tested. "

        Attachments

          Activity

            People

            Assignee:
            johan.wikman Johan Wikman
            Reporter:
            johan.wikman Johan Wikman
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.