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

MaxScale Memory Leak in Container

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not a Bug
    • Affects Version/s: 6.2.3
    • Fix Version/s: N/A
    • Component/s: N/A
    • Labels:
    • Environment:
      CentOS 7.7 Docker Container

      Description

      Customer has uncontrolled memory growth eventually leading to MaxScale exceeding its memory allocation and crashing.

      Problem is not reproducible outside customer's lab & production container environments. Customer is also unable to reproduce the problem in virtualization or bare metal environments. Customer states problem happens in "idle" state, where "idle" means between 55 and 250qps

      Successive efforts have ruled out MXS-4100 (non-zero connection_keepalive) and made an effort to minimize memory consumption by limiting write q high water mark as well as query classifier cache size. None of these changes have made a difference.

      Customer was shown how to run traces with jemalloc, added that to the container, and saw no change. two svg reports from different heap trace sessions attached.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              juan.vera Juan
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.