MySQL Bugs: #120000: Mysql crash after increase 2% innodb buffer pool

Bug #120000	Mysql crash after increase 2% innodb buffer pool
Submitted:	6 Mar 21:55	Modified:	8 Mar 13:19
Reporter:	Cesar Alzate	Email Updates:
Status:	Open	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	8.0.30-22	OS:	Ubuntu (22)
Assigned to:		CPU Architecture:	Any
Tags:	Swap = 0 in 8.0.30-22 for Linux on x86_64 (Percona Server (GPL)

Description:
we increased the innodb_buffer_pool 2% of the current value and the server was 65% of ram.  After we did that we received the confimation that the process was succesfully, howver the server crash without any message in alert or dmessages.

mysql> SHOW STATUS LIKE 'Innodb_buffer_pool_resize_status';
+----------------------------------+----------------------------------------------------+
| Variable_name                    | Value                                              |
+----------------------------------+----------------------------------------------------+
| Innodb_buffer_pool_resize_status | Completed resizing buffer pool at 260305 15:36:52. |
+----------------------------------+----------------------------------------------------+
1 row in set (16.72 sec)

We intentionally have no swap, some articles sugest me that was the cause of the issue.               
total        used        free      shared  buff/cache   available
Mem:            23Gi        20Gi       848Mi       1.0Mi       2.5Gi       2.9Gi
Swap:             0B          0B          0B

How to repeat:
we just try one time.

Suggested fix:
after bounce the server with new value mysql started working.

Sounds like kernel killed mysqld due to OOM (out of memory).
Please check /var/log/messages  logs to see if that was the case.

BTW, you should probably want to have a swap partition if server has small amount of RAM.

Related reading: https://anotherboringtechblog.com/2026/02/innodb-buffer-pool-chunk-size-calculator/

Would be good to have exact values of:
- innodb_buffer_pool_size
- innodb_buffer_pool_instances
- innodb_buffer_pool_chunk_size

And congrats on getting Bug#120000 !  :-)

I am adding the log and the innodb values requested:

+-------------------------------+-------------+
| Variable_name                 | Value       |
+-------------------------------+-------------+
| innodb_buffer_pool_chunk_size | 134217728   |
| innodb_buffer_pool_instances  | 8           |
| innodb_buffer_pool_size       | 22548578304 |
+-------------------------------+-------------+

I tried to increased innodb_buffer_pool_size to 25245508608(75 % ram).

no memory or panic messages in log:

grep -Ei "oom|out of memory|killed process|panic|watchdog|hung task|i/o error|ext4|xfs|nvme|reset" /var/log/syslog.1 | wc -l
0

last -x | head

cesar_al pts/0        xxx    Thu Mar  5 14:56 - crash  (00:51)