2020-01-07T18:49:22.140213+08:00 480475 [Warning] Slave SQL for channel '': Coordinator thread of multi-threaded slave is being stopped in the middle of assigning a group of events; deferring to exit until the group completion ... , Error_code: 0 2020-01-07T18:49:22.147381+08:00 480475 [Note] Slave SQL thread for channel '' exiting, replication stopped in log 'mysql-bin.015071' at position 799965177 2020-01-07T18:49:22.148168+08:00 480474 [Note] Slave I/O thread killed while reading event for channel '' 2020-01-07T18:49:22.148201+08:00 480474 [Note] Slave I/O thread exiting for channel '', read up to log 'mysql-bin.015071', position 800174417 2020-01-07T18:49:35.001849+08:00 1684425 [Note] Slave I/O thread: Start asynchronous replication to master 'ordersrepl@db-r1407-s4.ty8.huobiidc.com:3308' in log 'mysql-bin.015071' at position 800174417 2020-01-07T18:49:35.001957+08:00 1684425 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLA VE; see the 'START SLAVE Syntax' in the MySQL Manual for more information. 2020-01-07T18:49:35.002636+08:00 1684425 [Note] Slave I/O thread for channel '': connected to master 'ordersrepl@db-r1407-s4.ty8.huobiidc.com:3308',replication started in log 'mysql-bin.015071' at position 800174417 2020-01-07T18:49:35.026288+08:00 1684426 [Note] Slave SQL thread for channel '' initialized, starting replication in log 'mysql-bin.015071' at position 799965177, relay log '/hbdata/mysqldir3308/mylog/relay-bin.034933' position: 799965390 2020-01-07T18:51:35.065186+08:00 1684426 [Note] Multi-threaded slave statistics for channel '': seconds elapsed = 120; events assigned = 2381825; worker queues filled over overrun level = 0; waited due a Worker queue full = 0; waited due the total size = 0; waited at clock conflicts = 1192470600 waited (count) when Workers occupied = 77100 waited when Workers occupied = 63008325200 2020-01-07T18:53:11.350196+08:00 1684426 [Warning] Slave SQL for channel '': Coordinator thread of multi-threaded slave is being stopped in the middle of assigning a group of events; deferring to exit until the group completion ... , Error_code: 0 10:53:11 UTC - mysqld got signal 11 ; 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 https://bugs.percona.com/
key_buffer_size=67108864 read_buffer_size=33554432 max_used_connections=90 max_threads=5125 thread_count=29 connection_count=22 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 335682727 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f0aea9e0000 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 = 7f185cd3b9b8 thread_stack 0x40000 /opt/Percona-Server-5.7/bin/mysqld(my_print_stacktrace+0x2c)[0xeafeac] /opt/Percona-Server-5.7/bin/mysqld(handle_fatal_signal+0x479)[0xcea3a9] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f4b51a66390] /opt/Percona-Server-5.7/bin/mysqld(_ZNK14Relay_log_info22cannot_safely_rollbackEv+0xc4)[0xe73c94] /opt/Percona-Server-5.7/bin/mysqld[0xe59f24] /opt/Percona-Server-5.7/bin/mysqld(_Z22mts_checkpoint_routineP14Relay_log_infoybb+0xd1)[0xe6ba81] /opt/Percona-Server-5.7/bin/mysqld(_Z18slave_stop_workersP14Relay_log_infoPb+0x77f)[0xe6c59f] /opt/Percona-Server-5.7/bin/mysqld(handle_slave_sql+0x2e9)[0xe6c909] /opt/Percona-Server-5.7/bin/mysqld(pfs_spawn_thread+0x1b4)[0xec79c4] /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f4b51a5c6ba] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f4b4fbd841d]
Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0): is an invalid pointer Connection ID (thread ID): 1684426 Status: NOT_KILLED
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.
Environment
None
Attachments
2
Smart Checklist
Activity
Show:
Jira Bot May 16, 2020 at 7:57 PM
Hello , It's been 61 days since this issue went into Incomplete and we haven't heard from you on this.
At this point, our policy is to Close this issue, to keep things from getting too cluttered. If you have more information about this issue and wish to reopen it, please reply with a comment containing "jira-bot=reopen".
Jira Bot May 8, 2020 at 7:56 PM
Hello , It's jira-bot again. Your bug report is important to us, but we haven't heard from you since the previous notification. If we don't hear from you on this in 7 days, the issue will be automatically closed.
Jira Bot April 23, 2020 at 7:05 PM
Hello , I'm jira-bot, Percona's automated helper script. Your bug report is important to us but we've been unable to reproduce it, and asked you for more information. If we haven't heard from you on this in 3 more weeks, the issue will be automatically closed.
Lalit Choudhary March 16, 2020 at 10:01 AM
Hi
Tried to reproduce the described issue with PS 5.7.28 and using given my.cnf (MTS enabled, sem-sync rpl)
Started sysbench read-write load on master and ran stop slave; start slave in the loop with intervals, Ran this for a while and do not see any crash.
see if you can reproduce in this in your test environment.
abaowhy March 9, 2020 at 1:49 PM
This issue is hard to reproduce, it was replicated twice when stop slave was executed. The attachment is my.cnf
2020-01-07T18:49:22.140213+08:00 480475 [Warning] Slave SQL for channel '': Coordinator thread of multi-threaded slave is being stopped in the middle of assigning a group of events; deferring to exit until the group completion ... , Error_code: 0
2020-01-07T18:49:22.147381+08:00 480475 [Note] Slave SQL thread for channel '' exiting, replication stopped in log 'mysql-bin.015071' at position 799965177
2020-01-07T18:49:22.148168+08:00 480474 [Note] Slave I/O thread killed while reading event for channel ''
2020-01-07T18:49:22.148201+08:00 480474 [Note] Slave I/O thread exiting for channel '', read up to log 'mysql-bin.015071', position 800174417
2020-01-07T18:49:35.001849+08:00 1684425 [Note] Slave I/O thread: Start asynchronous replication to master 'ordersrepl@db-r1407-s4.ty8.huobiidc.com:3308' in log 'mysql-bin.015071' at position 800174417
2020-01-07T18:49:35.001957+08:00 1684425 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLA
VE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2020-01-07T18:49:35.002636+08:00 1684425 [Note] Slave I/O thread for channel '': connected to master 'ordersrepl@db-r1407-s4.ty8.huobiidc.com:3308',replication started in log 'mysql-bin.015071' at position 800174417
2020-01-07T18:49:35.026288+08:00 1684426 [Note] Slave SQL thread for channel '' initialized, starting replication in log 'mysql-bin.015071' at position 799965177, relay log '/hbdata/mysqldir3308/mylog/relay-bin.034933' position: 799965390
2020-01-07T18:51:35.065186+08:00 1684426 [Note] Multi-threaded slave statistics for channel '': seconds elapsed = 120; events assigned = 2381825; worker queues filled over overrun level = 0; waited due a Worker queue full = 0; waited due the total size
= 0; waited at clock conflicts = 1192470600 waited (count) when Workers occupied = 77100 waited when Workers occupied = 63008325200
2020-01-07T18:53:11.350196+08:00 1684426 [Warning] Slave SQL for channel '': Coordinator thread of multi-threaded slave is being stopped in the middle of assigning a group of events; deferring to exit until the group completion ... , Error_code: 0
10:53:11 UTC - mysqld got signal 11 ;
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 https://bugs.percona.com/
key_buffer_size=67108864
read_buffer_size=33554432
max_used_connections=90
max_threads=5125
thread_count=29
connection_count=22
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 335682727 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f0aea9e0000
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 = 7f185cd3b9b8 thread_stack 0x40000
/opt/Percona-Server-5.7/bin/mysqld(my_print_stacktrace+0x2c)[0xeafeac]
/opt/Percona-Server-5.7/bin/mysqld(handle_fatal_signal+0x479)[0xcea3a9]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f4b51a66390]
/opt/Percona-Server-5.7/bin/mysqld(_ZNK14Relay_log_info22cannot_safely_rollbackEv+0xc4)[0xe73c94]
/opt/Percona-Server-5.7/bin/mysqld[0xe59f24]
/opt/Percona-Server-5.7/bin/mysqld(_Z22mts_checkpoint_routineP14Relay_log_infoybb+0xd1)[0xe6ba81]
/opt/Percona-Server-5.7/bin/mysqld(_Z18slave_stop_workersP14Relay_log_infoPb+0x77f)[0xe6c59f]
/opt/Percona-Server-5.7/bin/mysqld(handle_slave_sql+0x2e9)[0xe6c909]
/opt/Percona-Server-5.7/bin/mysqld(pfs_spawn_thread+0x1b4)[0xec79c4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f4b51a5c6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f4b4fbd841d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 1684426
Status: NOT_KILLED
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.