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

Memory leak in 6.4.2

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 6.4.2, 6.4.4
    • N/A
    • maxbase
    • None
    • Debian OS 11.3
    • MXS-SPRINT-171, MXS-SPRINT-172, MXS-SPRINT-173, MXS-SPRINT-174, MXS-SPRINT-179, MXS-SPRINT-180, MXS-SPRINT-181, MXS-SPRINT-182, MXS-SPRINT-183, MXS-SPRINT-204, MXS-SPRINT-205, MXS-SPRINT-206, MXS-SPRINT-207, MXS-SPRINT-208

    Description

      Hi Team,

      We see a linear increase of ram usage, finally crashing maxscale at 100% ram usage..

      The maxscale process was killed by the oom_killer.. Here I have attached the maxsclae config file and memory usage graphs.. Please check it..

      Attachments

        Issue Links

          split to

          Bug - A problem which impairs or prevents the functions of the product. MXS-5103 query_classifier_cache_size=0 with short connections appears to leak memory

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            People

              markus makela markus makela
              ponsuresh.pandians Pon Suresh Pandian (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              9 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.