[MDEV-8933] slave crashed when execute stop slave Created: 2015-10-13  Updated: 2015-10-21  Resolved: 2015-10-21

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.0
Fix Version/s: 10.0.18

Type: Bug Priority: Major
Reporter: Zhoukai Lin Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-7864 [PATCH] Slave SQL: stopping on non-la... Closed

 Description   

I executed a big transaction in the master,like insert into t1 select * from t2.When the slave is doing replay,I execute stop slave, it's very easy to cause the slave crash.
Here is error log:

150922 18:53:50 [ERROR] 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.
 
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
 
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.
 
Server version: 10.0.12-MariaDB-log
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=4
max_threads=153
thread_count=4
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 154596 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0x7f01f082b008
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 = 0x7f023f920d58 thread_stack 0x48000
mysys/stacktrace.c:247(my_print_stacktrace)[0xa9fbe9]
sql/signal_handler.cc:153(handle_fatal_signal)[0x6dd66a]
/lib64/libpthread.so.0[0x3bca00f710]
sql/rpl_rli.h:650(rpl_group_info::free_annotate_event())[0x646767]
sql/slave.cc:4694(handle_slave_sql)[0x539637]
/lib64/libpthread.so.0[0x3bca0079d1]
/lib64/libc.so.6(clone+0x6d)[0x3bc98e8b6d]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0): 
Connection ID (thread ID): 16
Status: NOT_KILLED
 
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on
 
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.



 Comments   
Comment by Elena Stepanova [ 2015-10-17 ]

You might be hitting the bug MDEV-7864 (fixed in 10.0.18).

The version 10.0.12 that you are using is more than a year old, do you consider upgrading to the recent 10.0 release? If so, please let us know whether the problem disappars after the upgrade.

Comment by Zhoukai Lin [ 2015-10-21 ]

I tested this on 10.0.21, the slave didn't crashed.

Comment by Elena Stepanova [ 2015-10-21 ]

Fixed in scope of MDEV-7864.

Generated at Thu Feb 08 07:30:53 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.