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

Potential memory leak

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.10
    • Fix Version/s: 2.5.12
    • Component/s: maxctrl
    • Labels:
      None
    • Environment:
      Red Hat Enterprise Linux 8.3 (Ootpa)
      Intel(R) Xeon(R) Gold 6278C CPU @ 2.60GHz
      8gb ram
    • Sprint:
      MXS-SPRINT-139

      Description

      memory usage seems to grow overtime in maxscale,
      2 os memory graph one is taken around 11 am another one around 12 pm
      growing from 41% to 54% in m one hour time.

      while the backend galera cluster stable at 5.5% ram usage.

        Attachments

        1. maxscle.png
          maxscle.png
          16 kB
        2. os_.jpg
          os_.jpg
          59 kB
        3. os memory.jpg
          os memory.jpg
          61 kB

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            cyngate Chin Yuen
            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.