Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-20933

Querying information_schema leads to memory leak

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.2.27
    • None
    • Information Schema
    • mysql Ver 15.1 Distrib 10.2.27-MariaDB, for Linux (x86_64) using readline 5.1
      CentOS Linux release 7.7.1908 (Core)
      MariaDB-server-10.2.27-1.el7.centos.x86_64

    Description

      Upon querying information_schema, the memory footprint of the database process increases until it is killed by the OOM handler

      Reproducible by:

      $ /bin/ps -ylC mysqld | /bin/awk '{x += $8;y += 1} END {print "Memory Usage (MB): "x/1024, "\n\n"}'; sudo -H mysql -e "select sum(data_length+index_length) from information_schema.tables where engine='memory';";/bin/ps -ylC mysqld | /bin/awk '{x += $8;y += 1} END {print "Memory Usage (MB): "x/1024, "\n\n"}';
      Memory Usage (MB): 3740.43 
       
       
      +-------------------------------+
      | sum(data_length+index_length) |
      +-------------------------------+
      |                             0 |
      +-------------------------------+
      Memory Usage (MB): 6195.26 
      

      Affected customer has 227 databases, with ~22 tables each

      Attachments

        Activity

          People

            Unassigned Unassigned
            proserve_support Proserve (operations)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.