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

OOM on slave, allocating all available memory

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6.3
    • None
    • Server
    • CentOS 7.9 64 bit x64_64, 128Gb RAM

    Description

      My replication slave starts allocating all memory once it has reached a certain binlog position. It looks like there is a very large transaction ( affecting >100.000 rows) which ran fine on the master causing this.
      I simplified my config already to almost defaults, lowered the pool size and tried playing with max_binlog_cache_size and max_binlog_stmt_cache_size to no avail.

      What other info can I supply in order to better diagnose this?

      (NB I set MemoryLimit to 70G in limits.conf hence the messages.log showing the OOM at 73400320kB)

      Attachments

        Activity

          People

            Unassigned Unassigned
            Betel Michiel
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.