Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.11.12, 11.4.6, 11.8.2
-
Linux, FreeBSD
-
Can result in unexpected behaviour
-
After a successful execution of SET GLOBAL innodb_buffer_pool_size, the buffer pool would be included in future core dumps, contrary to the expectation on Linux and FreeBSD.
Description
By default we expect that innodb_buffer_pool will not be part of core_file in release builds. (MDEV-10814)
Fix for MDEV-38671 kind of breaks this.. The core file which used to be around 0.5G is now about 1.5G with the MDEV-38671 fix.
tafzeel at myWorkstation in 10_11_server
|
$ ./sql/mariadbd --datadir=$__DATADIR --log-error=$__DATADIR/mysql.log --core-file=1 --innodb-buffer-pool-size=1G &
|
[1] 68083
|
|
|
tafzeel at myWorkstation in 10_11_server
|
$ kill -SIGABRT 68083
|
|
|
tafzeel at myWorkstation in 10_11_server
|
$ ls -lh data/core.68083
|
-rw------- 1 tafzeel tafzeel 1.4G Mar 3 17:16 data/core.68083
|
MariaDB [(none)]> SELECT VERSION();
|
+------------------+
|
| VERSION() |
|
+------------------+
|
| 10.11.17-MariaDB |
|
+------------------+
|
1 row in set (0.000 sec)
|
Attachments
Issue Links
- blocks
-
MDEV-22186 Add innodb_trim_core_file to exclude InnoDB memory from cores
-
- In Progress
-
- is caused by
-
MDEV-29445 reorganise innodb buffer pool (and remove buffer pool chunks)
-
- Closed
-
-
-
- Closed
-