[MDEV-11049] Server crash when dynamic replication strings are set to NULL Created: 2016-10-13  Updated: 2016-10-13  Resolved: 2016-10-13

Status: Closed
Project: MariaDB Server
Component/s: Admin statements, Replication
Affects Version/s: 10.1.18
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Brian Evans Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MDEV-8329 MariaDB crashes when replicate_wild_i... Closed

 Description   

With the statement 'SET GLOBAL replicate_do_db=NULL', the server crashes with the following backtrace:

161013  9:08: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 https://mariadb.com/kb/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.1.14-MariaDB
key_buffer_size=33554432
read_buffer_size=262144
max_used_connections=6
max_threads=1001
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 805576 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0x7f639774c008
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 = 0x7f63d8064dc8 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x20)[0x55f828be2b80]
/usr/sbin/mysqld(handle_fatal_signal+0x347)[0x55f828760c7f]
/lib64/libpthread.so.0(+0x103b0)[0x7f63d98233b0]
/usr/sbin/mysqld(my_strdup+0x13)[0x55f828bdf5ac]
/usr/sbin/mysqld(_ZN10Rpl_filter17parse_filter_ruleEPKcMS_FiS1_E+0x24)[0x55f828595a66]
/usr/sbin/mysqld(_ZN10Rpl_filter9set_do_dbEPKc+0x2f)[0x55f828596611]
/usr/sbin/mysqld(_ZN18Sys_var_rpl_filter16set_filter_valueEPKcP11Master_info+0x35)[0x55f8286d7849]
/usr/sbin/mysqld(_ZN18Sys_var_rpl_filter13global_updateEP3THDP7set_var+0x126)[0x55f8286d79bc]
/usr/sbin/mysqld(_ZN7sys_var6updateEP3THDP7set_var+0x82)[0x55f8285971a4]
/usr/sbin/mysqld(_ZN7set_var6updateEP3THD+0x17)[0x55f828597547]
/usr/sbin/mysqld(_Z17sql_set_variablesP3THDP4ListI12set_var_baseEb+0xa1)[0x55f8285986fe]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x350f)[0x55f828607b8a]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x167)[0x55f82860afb1]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xbdc)[0x55f82860c357]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1b9)[0x55f82860dff4]
/usr/sbin/mysqld(_Z26threadpool_process_requestP3THD+0x67)[0x55f828709184]
/usr/sbin/mysqld(+0x53eda5)[0x55f82873eda5]
/usr/sbin/mysqld(+0x53f629)[0x55f82873f629]
/lib64/libpthread.so.0(+0x730c)[0x7f63d981a30c]
/lib64/libc.so.6(clone+0x6d)[0x7f63d845352d]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f637400d020): is an invalid pointer
Connection ID (thread ID): 2060
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



 Comments   
Comment by Elena Stepanova [ 2016-10-13 ]

Thanks. We already have it filed as MDEV-8329. I'll raise the priority for that issue.

Comment by Brian Evans [ 2016-10-13 ]

It seems that several dynamic strings in replication cause the crash.

replicate_do_db, replicate_do_table, replicate_ignore_db, replicate_ignore_table, replicate_wild_ignore_table, replicate_wild_do_table

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