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

Memory leak in 2.4.17?

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4.17
    • Fix Version/s: N/A
    • Component/s: QueryClassifier
    • Labels:
      None
    • Environment:
      Kubernetes
    • Sprint:
      MXS-SPRINT-145, MXS-SPRINT-146

      Description

      We were using 2.5.15 and having good success with it. Unfortunatly, we needed to downgrade to 2.4.17 because we need to use the the weighty keyword. When we downgraded, it seems like we have a memory leak going on.

      Since downgrading. we added the weighby keyword and that's has been working. but memory just grows. On rare occasion, I will see memory go down but it usually goes right back up. We have set the limit to 1g and its still running out of memory. We plan to run add to 2g to see while we debug but concerned that wont be enough.

      I am looking for a bit of help to figure out whats taking all this memory. When I look at qc_cache_size it looks like its 300K per thread. (4)
      │ QC cache size │ 299956 │

      We don't have the cache even set up. [Cache]

      So I cant figure out where memory is even going?

      Here is our memory footprint for maxscale. (yes we have 7 versions running)

      The drops are going to be when its OOMKilled when it goes over 1g.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              jsmelser_recharge Jeff Smelser
              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.