crash resizing the innodb_buffer_pool

[monty solomon]

I resized the innodb_buffer_pool and the server crashed.

mysql> select @@innodb_buffer_pool_size;
+---------------------------+
| @@innodb_buffer_pool_size |
+---------------------------+
| 55834574848 |
+---------------------------+
1 row in set (0.00 sec)

mysql> set global innodb_buffer_pool_size=25769803776;
Query OK, 0 rows affected (0.01 sec)

[monty solomon (monty+launchpad)]

InnoDB: ###### Diagnostic info printed to the standard error stream
2016-08-29T22:41:43.963670Z 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
2016-08-29 22:41:43 0x7fd41ffff700 InnoDB: Assertion failure in thread 140549046662912 in file ut0ut.cc line 921
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xec501c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x79d141]
/lib64/libpthread.so.0(+0xf7e0)[0x7fe20c60c7e0]
/lib64/libc.so.6(gsignal+0x35)[0x7fe20a846625]
/lib64/libc.so.6(abort+0x175)[0x7fe20a847e05]
/usr/sbin/mysqld[0x76bd86]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0xee)[0x114b91e]
/usr/sbin/mysqld(srv_error_monitor_thread+0xe50)[0x10e7200]
/lib64/libpthread.so.0(+0x7aa1)[0x7fe20c604aa1]
/lib64/libc.so.6(clone+0x6d)[0x7fe20a8fc93d]
2016-08-29T22:41:47.828145Z mysqld_safe Number of processes running now: 0
2016-08-29T22:41:47.829871Z mysqld_safe mysqld restarted

[monty solomon (monty+launchpad)]

22:41:43 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=67108864
read_buffer_size=1048576
max_used_connections=27
max_threads=701
thread_count=21
connection_count=19
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 971371 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.

[monty solomon (monty+launchpad)]

mysql Ver 14.14 Distrib 5.7.13-6, for Linux (x86_64) using 6.0
Server version: 5.7.13-6-log Percona Server (GPL), Release 6, Revision e3d58bb
CentOS release 6.7 (Final)
Linux shaky-cat 3.18.36.el6.x86_64 #1 SMP Tue Aug 9 18:09:42 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[monty solomon (monty+launchpad)]

The bug status is still Undecided. Has this bug been triaged?

[monty solomon (monty+launchpad)]

The bug status is still New/Undecided. Has this bug been triaged?

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3539