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

decreasing innodb_buffer_pool_size at runtime does not release memory

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.5.21
    • 10.5
    • Server
    • None

    Description

      After reducing the value of innodb_buffer_pool_size at runtime from 90G to 50G with "set global", the memory is not released to system, OOM event strikes.

      Happened to multiple servers with same configuration.

      other relevant variables:

      innodb_buffer_pool_chunk_size=134217728
      innodb_buffer_pool_instances=1

      Attachments

        Issue Links

          Activity

            MariaDB Server 10.5 only supports InnoDB buf_pool instance. If I remember it correctly, the initially allocated buffer pool chunk can never be released. The data structures would be greatly simplified in MDEV-29445, where I intend to allocate one contiguous range of virtual memory addresses for the entire buffer pool.

            marko Marko Mäkelä added a comment - MariaDB Server 10.5 only supports InnoDB buf_pool instance. If I remember it correctly, the initially allocated buffer pool chunk can never be released. The data structures would be greatly simplified in MDEV-29445 , where I intend to allocate one contiguous range of virtual memory addresses for the entire buffer pool.

            The chunk size in this case is default 128M, this does not explain the behaviour... if "initially allocated" means the first chunk

            rpizzi Rick Pizzi (Inactive) added a comment - The chunk size in this case is default 128M, this does not explain the behaviour... if "initially allocated" means the first chunk

            People

              marko Marko Mäkelä
              rpizzi Rick Pizzi (Inactive)
              Votes:
              1 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.