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

Memory Limit reached causes mariadb server restart

Details

    • Task
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • Configuration
    • None

    Description

      The configuration looks like this:

      systemctl edit mariadb.service

      add the following for example

       
      systemctl edit mariadb.service
       
      [Service]
      MemoryMax=18000M
      MemorySwapMax=750M
       
       
      systemctl daemon-reload
       
      or vi(m) / nano
       
      nano /etc/systemd/system/mariadb.service.d/override.conf
      

      If the memory limit is reached, the server crashes and restarts.

      This memory limit behaves as if there was no more memory available on the system.

      Could memory drain intelligence be improved?

      Attachments

        Issue Links

          Activity

            Yes, MariaDB needs to have better checks for out-of-memory conditions.
            In case of bigger allocations, MariaDB will detect that and give an error to end user.
            However if one cannot allocate any memory even for small things, then MariaDB may crash.
            This is something we have to improve over time.

            monty Michael Widenius added a comment - Yes, MariaDB needs to have better checks for out-of-memory conditions. In case of bigger allocations, MariaDB will detect that and give an error to end user. However if one cannot allocate any memory even for small things, then MariaDB may crash. This is something we have to improve over time.

            People

              Unassigned Unassigned
              Horus Sirius Jan Bludau
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.