Bug #98887 MySQL 5.7.27 stop slave Failing assertion: UT_LIST_GET_LEN
Submitted: 10 Mar 9:08 Modified: 9 Apr 14:12
Reporter: Anthony Qiu Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.7.27 OS:CentOS (CentOS release 6.10 (Final))
Assigned to: MySQL Verification Team CPU Architecture:x86 (Intel(R) Xeon(R) CPU E5-2687W v4 @ 3.00GHz)

[10 Mar 9:08] Anthony Qiu
5.7.27 slave, an assertion error occurred executing the command "stop slave or shutdown()".

2020-03-10 11:13:04 0x2b1a33ba4300  InnoDB: Assertion failure in thread 47391536988928 in file trx0rseg.cc line 134
InnoDB: Failing assertion: UT_LIST_GET_LEN(rseg->update_undo_list) == 0
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.
03:13:04 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.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 147504340 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
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.

--- slave configure
master_info_repository = TABLE
relay_log_info_repository = TABLE
sync_binlog = 1
gtid_mode = 0
enforce_gtid_consistency = 0
binlog_format = row
relay_log = relay-log
relay_log_recovery = 1
slave_skip_errors = ddl_exist_errors
slave-rows-search-algorithms = 'INDEX_SCAN,HASH_SCAN'
loose_innodb_numa_interleave = 1
innodb_buffer_pool_dump_pct = 40
innodb_page_cleaners = 12
innodb_undo_log_truncate = 1
innodb_max_undo_log_size = 2G
innodb_purge_rseg_truncate_frequency = 128
slave-parallel-type = LOGICAL_CLOCK
slave-parallel-workers = 0

How to repeat:
"stop slave or shutdown()" command
[9 Apr 14:12] MySQL Verification Team
Hi Anthony,

This is not a software bug, this is a memory corruption bug that caused InnoDB to crash. Do you have registered ECC RAM on your server or you are running a plain RAM without any error checking? Chance of this crash happening again is very slim and not much we can do about it. If, on the other hand, you do run your server with error checking RAM then we really need to know what you did and how to reproduce this.

Stay safe