Bug #115024 MySQL Crash occurs during MySQL Replication stop process
Submitted: 16 May 2024 5:04 Modified: 17 May 2024 20:46
Reporter: young duk park Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:8.0.33 OS:Linux (Rocky Linux release 8.9)
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: Mysql Crashed, repliation, replication slave start-stop

[16 May 2024 5:04] young duk park
Description:
1. Phenomenon

1) MySQL Crash occurs while stopping replication in Slave DB.
※ Command: mysqladmin --user=xxx --password=xxx stop-replica

2) Check the following message in the error log
2024-05-14T19:00:03Z UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=2322a98ee785d298cbc399f95a31b9671531a40b
Thread pointer: 0x7f939ce3bba0
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...
2024-05-15T04:00:03.526546+09:00 4277397 [Note] [MY-010587] [Repl] Replica SQL thread for channel '' exiting, replication stopped in log 'mysql-bin.030014' at position 11072137
stack_bottom = 7fa5e811bc10 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x2124331]
/usr/sbin/mysqld(print_fatal_signal(int)+0x2a2) [0xfe7bc2]
/usr/sbin/mysqld(handle_fatal_signal+0xa5) [0xfe7d75]
/lib64/libpthread.so.0(+0x12cf0) [0x7fa5f8d2ecf0]
/lib64/libpthread.so.0(pthread_kill+0xa) [0x7fa5f8d2ba0a]
/usr/sbin/mysqld() [0x1e11106]
/usr/sbin/mysqld(terminate_slave_threads(Master_info*, int, unsigned long, bool)+0xd2) [0x1e153c2]
/usr/sbin/mysqld(stop_slave(THD*, Master_info*, bool, bool, bool*)+0x235) [0x1e1b965]
/usr/sbin/mysqld(stop_slave(THD*)+0x1a3) [0x1e1bdb3]
/usr/sbin/mysqld(stop_slave_cmd(THD*)+0xa6) [0x1e23b06]
/usr/sbin/mysqld(mysql_execute_command(THD*, bool)+0x2eff) [0xe7b7bf]
/usr/sbin/mysqld(dispatch_sql_command(THD*, Parser_state*)+0x51b) [0xe7cb9b]
/usr/sbin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0x233d) [0xe7f4cd]
/usr/sbin/mysqld(do_command(THD*)+0x15b) [0xe8005b]
/usr/sbin/mysqld() [0xfd7dc8]
/usr/sbin/mysqld() [0x2833eb4]
/lib64/libpthread.so.0(+0x81ca) [0x7fa5f8d241ca]
/lib64/libc.so.6(clone+0x43) [0x7fa5f70c7e73]

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

2. Related DB settings (my.cnf)

binlog_format = ROW
log_replica_updates
replica_parallel_workers = 0

How to repeat:
Described above
[16 May 2024 9:55] MySQL Verification Team
HI MR. park,

Thank you for your bug report.

Please, let us inform you that this is a forum for the reports with fully repeatable test cases. A test case is required to consist of the set of SQL statements and configurations that always leads to the big that is reported.

We are waiting on your test case.