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

Memory leak in 2.4.8 - each next day dozens of MB

    XMLWordPrintable

Details

    Description

      Hi,

      few days ago we upgraded from MaxScale 2.4.x to latest 2.4.8 and also from "readconnroute" to "readwritesplit".

      I attached our maxscale.cnf and chart where is visible RSS RAM of MaxScale. After each midnight RSS increased dozens of MB. 3 days ago i restarted MaxScale - this is reason why memory was so low/cleared.

      We have this maxscale.cnf on multiple servers/clients with MaxScale 2.4.8 and all of them have this memory leak.

      I can provide you result of any maxctrl/other command, which can help you.

      UPDATE: i attached still one screenshot from another project/server with same maxscale.conf. We imported one database from another server (148 InnoDB tables, approx. 18 million records and 1.5 GB of data in total). MaxScale memory increased from ~85 MB to ~388 MB. Maybe it's based on same reason, maybe not.

      Thank you.

      Attachments

        1. db-master-slave-queries.png
          62 kB
          Ján Regeš
        2. maxscale-2.4.8-memory-leak.png
          19 kB
          Ján Regeš
        3. maxscale-2.4.8-memory-leak-after-db-import.png
          23 kB
          Ján Regeš
        4. maxscale-ab-last-21-days.png
          285 kB
          Ján Regeš
        5. maxscale-hc-last-21-days.png
          254 kB
          Ján Regeš
        6. maxscale-iw-last-21-days.png
          304 kB
          Ján Regeš
        7. maxscale-memory-leak.cnf
          2 kB
          Ján Regeš

        Activity

          People

            markus makela markus makela
            jan.reges Ján Regeš
            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.