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

Randomly using all available memory after OS upgrade

    XMLWordPrintable

Details

    • Bug
    • Status: Needs Feedback (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.11.7
    • None
    • Server
    • None
    • CentOS Stream 9

    Description

      We have about 200 web servers that were running MariaDB 10.11 on CentOS 7. After upgrading them to CentOS Stream 9, we immediately started seeing this issue. At random times, the memory usage of MariaDB will increase until it completely fills up the RAM and then crashes. This happens very rapidly and uses GBs of RAM at a time.

      Before the upgrades, it was running fine. No change in data or traffic levels. And this wasn't an in-place OS upgrade or anything. We spun up a new server with the new OS and just migrated the data to the new servers. Pretty standard.

      As for the config used with Mariadb, it's fairly standard but we've tried going back to the default config as well. No change.

      There is 1 thing I've found that fixes the problem and that is swapping out the official repo version with the official Mariadb container using Docker. I ran 1 of these servers for 1 week using the container and it fully solved the problem. No more big memory spikes.

      So there appears to be some kind of problem with Mariadb 10.11 on CentOS Stream 9. I'm having trouble even getting any data out of this that could be useful in solving the problem.

      Any advice on how to gather some valuable data on this issue? Or any ideas on what could be the underlying cause?

      Attachments

        Activity

          People

            Unassigned Unassigned
            wk_bradp Brad
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.