Bug #97387 mysql innodb cluster crash, mysql restart failed
Submitted: 26 Oct 2019 1:25 Modified: 26 Oct 2019 12:05
Reporter: black 无 Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:8.0.17 OS:CentOS (7.7)
Assigned to: CPU Architecture:Any

[26 Oct 2019 1:25] black 无
Description:
3 nodes, 2 at the same time crash, and the restart failed

InnoDB: Progress in percents: 110:07:32 UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7f3ad8a95980
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 = 7f453fcfeba0 thread_stack 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x1f104dd]
/usr/sbin/mysqld(handle_fatal_signal+0x333) [0xf8b933]
/lib64/libpthread.so.0(+0xf5f0) [0x7f4b91ada5f0]
/usr/sbin/mysqld(dtuple_convert_big_rec(dict_index_t*, upd_t*, dtuple_t*, unsigned long*)+0xb62) [0x2279e02]
/usr/sbin/mysqld(btr_cur_pessimistic_update(unsigned long, btr_cur_t*, unsigned long**, mem_block_info_t**, mem_block_info_t*, big_rec_t**, upd_t*, unsigned long, que_thr_t*, unsigned long, unsigned long, mtr_t*)+0x2ef) [0x21fc59f]
/usr/sbin/mysqld() [0x236f926]
/usr/sbin/mysqld() [0x2370047]
/usr/sbin/mysqld(row_undo_mod(undo_node_t*, que_thr_t*)+0xcbf) [0x237331f]
/usr/sbin/mysqld(row_undo_step(que_thr_t*)+0x60) [0x213bb40]
/usr/sbin/mysqld(que_run_threads(que_thr_t*)+0x988) [0x20cbb08]
/usr/sbin/mysqld(trx_rollback_or_clean_recovered(unsigned long)+0xbba) [0x219affa]
/usr/sbin/mysqld(trx_recovery_rollback_thread()+0x30) [0x219c020]
/usr/sbin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Runnable, void (*)()> > >::_M_run()+0xb5) [0x2072995]
/usr/sbin/mysqld() [0x263cf3f]
/lib64/libpthread.so.0(+0x7e65) [0x7f4b91ad2e65]
/lib64/libc.so.6(clone+0x6d) [0x7f4b8fc5988d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
unknown
[26 Oct 2019 12:05] Miguel Solorzano
Thank you for the bug report. We need a complete repeatable test case to process this bug report, please when you will able provide it here, also test the latest release.