Percona Server moved to https://jira.percona.com/projects/PS

Use MADV_DONTDUMP for innodb buffer pool

Series 5.1
Bug #1092645

Bug #1092645 reported by Raghavendra D Prabhu on 2012-12-20

This bug affects 2 people

	Status	Importance	Assigned to
MySQL Server	Unknown	Unknown	mysql-bugs #66826
Percona Server moved to https://jira.percona.com/projects/PS	Status tracked in 5.7
5.1	Won't Fix	Wishlist	Unassigned
5.5	Triaged	Wishlist	Unassigned
5.6	Triaged	Wishlist	Unassigned
5.7	Triaged	Wishlist	Unassigned

Bug Description

Linux 3.4 onwards supports MADV_DONTDUMP with madvise. This can be used to
mark the entire buffer pool as DONTDUMP. This is/will be really
helpful in situations with over-sized buffer pools in getting
smaller coredumps. I guess this can be made global variable,
however, I don't see many situations where one wants to
investigate the buffer pool contents themselves.

Tags:

Laurynas Biveinis (laurynas-biveinis) on 2012-12-21

no longer affects:

mysql-server

Revision history for this message

Valerii Kravchuk (valerii-kravchuk) wrote on 2012-12-21:

See http://crpppc19.epfl.ch/cgi-bin/man/man2html?2+madvise for reference, for example.

Valerii Kravchuk (valerii-kravchuk) on 2013-10-24

tags:

added: i35022

Revision history for this message

Hui Liu (hickey) wrote on 2014-02-28:

innodb_dump_full_corefile.patch Edit (11.4 KiB, text/plain)

low-hang-fruit :)

Revision history for this message

Hui Liu (hickey) wrote on 2014-02-28:

patch is based on mysql-5.6.16

Revision history for this message

Hui Liu (hickey) wrote on 2014-02-28:

innodb_dump_full_corefile=ON:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
15066 xiyu.lh 20 0 24.4g 12g 8428 S 0.0 77.6 43:13.70 mysqld

  kill -11 15066
  $ du -hs data/core.15066
  13G data/core.15066

  innodb_dump_full_corefile=OFF:
    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
   8259 xiyu.lh 20 0 24.4g 12g 8464 S 0.0 77.3 43:41.62 mysqld
  kill -11 8259
  $ du /u01/my56/data/core.8259 -hs
  2.5G /u01/my56/data/core.8259