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

Growing memory consumption with 2.2.17

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.2.17
    • Fix Version/s: 2.2.18
    • Component/s: Core
    • Labels:
    • Environment:
      Debian 8.6
    • Sprint:
      MXS-SPRINT-72

      Description

      We have just upgraded from 2.0.2 to 2.2.17 and have spotted an immediate growing memory consumption. On 2.0.2 it was constant, around 400MB (instance running for about two years nonstop):

      But as soon as we switched over to 2.2.17, the consumption started rising and seems to be rising until it OOM killer kicks in:

      There has been no change in traffic, type of traffic, amount of clients, connections, amount and types of queries etc. We're running readwritesplit service with slave_selection_criteria=LEAST_CURRENT_OPERATIONS router options and galeramon, configuration settings unchanged since 2.0.2.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              mensonen Mikko Mensonen
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.