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

maxscale possible memory leak

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Not a Bug
    • 1.4.1
    • 1.4.1
    • readwritesplit
    • None
    • Centos 6.7

    Description

      Hi,

      we are running MaxScale version 1.4.1 with an application using hibernate and MaxScale is being killed roughly every 30 Min by OS because it is consuming to much memory.

      I think it is related to the MySQL session/global variables.

      Hibernate does the following things, when running selects:

      set autocommit=0;
      select * from table;
      set autocommit=1;
      

      i tried to reproduce it with a simple bash-loop, and the ram usage is rapidly increasing:

      while true; do mysql -B -N -h 127.0.0.1 -u maxscale --port 4008 -e "set autocommit=0; select 1;" && mysql -B -N -h 127.0.0.1 -u maxscale --port 4008 -e "set autocommit=1; select 2;"; done
      

      setting maxsec-cmd-history is not a solution for me, becaus the first values will soon be overwritten

      i did not check the same thing during one session, maybe this has to be done.

      Regards, Michael

      Attachments

        Activity

          People

            Unassigned Unassigned
            bx_froehlichm Michael Froehlich
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.