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

Feature request: Optionally exclude large buffers from core dumps

    XMLWordPrintable

    Details

      Description

      As the size of core dump files by default mostly equals the process size producing core dumps can become an issue on systems with memory buffers, esp. large innodb_buffer_pool_size.

      There needs to be enough file system space to store such large core dumps, and with multi gigabyte files it also takes a non-trivial amount of time to write these, so delaying process restart quite a bit.

      And then there's also a security aspect to it: as the core dump contains the complete innodb buffer pool it contains a substantial amount, or even all, of the actual user data in the database.

      At the same time actual buffer contents are rarely needed when doing a post mortem analysis (usually we only need stack frames and a few pieces of local data).

      So I'm proposing a server option to exclude certain buffers from core dumps by marking them as DONOTDUMP with the madvise() system call.

        Attachments

          Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18946 munmap of 1 byte during shutdown is EINVAL

          • Major - Major loss of function.
          • Closed
          relates to

          Task - A task that needs to be done. MDEV-17159 Document what is included in core dumps

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-16605 Always include buf_madvise_do_dump in binaries.

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-20684 innodb: use madvise CORE/NOCORE on FreeBSD for selective large allocations

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21741 [Warning] InnoDB: Failed to set memory to MADV_DONTDUMP: Function not implemented

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

            Activity

              People

              Assignee:
              sanja Oleksandr Byelkin
              Reporter:
              hholzgra Hartmut Holzgraefe
              Votes:
              4 Vote for this issue
              Watchers:
              11 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Resolved: