Galera cluster crash when running 'set session wsrep_osu_method=RSU' using Perl

39 views
Skip to first unread message

julien an

unread,
Dec 20, 2016, 10:11:19 AM12/20/16
to codership
I wrote a perl script to run an ANALYZE for a table, all tables in a database, or all tables in all databases. I noticed that the Galera cluster node crashes systematically when executing the second iteration of the analyze command in "Rolling Schema Upgrade".
If I do not execute the "set session wsrep_OSU_method='RSU';" command the script works.

Operating System SUSE 11, Perl 5.1.6.3, MySQL 5.6.29, wsrep_25.14

if ($isGalera) {
   $stmt = "set session wsrep_OSU_method='RSU';" ;
   $dbh->do($stmt) or die "Error......";
}

my ($ope)="";
$stmt = "select table_schema, table_name, engine from information_schema.tables  WHERE ((table_name='${tabname}' and char_length('${tabname}') > 0) or char_length('${tabname}') = 0) and ((table_schema='${dbname}' and char_length('${dbname}') > 0) or char_length('${dbname}') = 0) and (table_schema not in ('mysql', 'information_schema', 'performance_schema')) and table_type = 'BASE TABLE';";
$sth = $dbh->prepare($stmt) or die "Error......";
$sth->execute() or die "Error......";
while(my @row = $sth->fetchrow_array()) {
   $ope = "analyze table \`$row[0]\`.\`$row[1]\`;" ;
   $dbh->do($ope) or die "Error......";
}
$sth->finish;
$dbh->disconnect();


2016-12-20 15:56:38 11821 [ERROR] WSREP: FSM: no such a transition JOINED -> DONOR
14:56:38 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.
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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=10
max_threads=151
thread_count=10
connection_count=10
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76375 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x24efa70
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 = 7f09a187de38 thread_stack 0x30000
/soft/mys56g/bin/mysqld(my_print_stacktrace+0x35)[0x944a15]
/soft/mys56g/bin/mysqld(handle_fatal_signal+0x41b)[0x68a51b]
/lib64/libpthread.so.0(+0xf850)[0x7f0a969da850]
/lib64/libc.so.6(gsignal+0x35)[0x7f0a955f5875]
/lib64/libc.so.6(abort+0x181)[0x7f0a955f6e51]
/soft/mys56g/lib/libgalera_smm.so(_ZN6galera3FSMINS_10Replicator5StateENS_13ReplicatorSMM10TransitionENS_10EmptyGuardENS_11EmptyActionEE8shift_toES2_+0x17e)[0x7f0a77b16d8e]
/soft/mys56g/lib/libgalera_smm.so(_ZN6galera13ReplicatorSMM6desyncEv+0x62)[0x7f0a77b0d562]
/soft/mys56g/lib/libgalera_smm.so(galera_desync+0x18)[0x7f0a77b1c238]
/soft/mys56g/bin/mysqld(_Z24wsrep_to_isolation_beginP3THDPcS1_PK10TABLE_LIST+0xa29)[0x5acab9]
/soft/mys56g/bin/mysqld(_ZN21Sql_cmd_analyze_table7executeEP3THD+0x12b)[0x86fe9b]
/soft/mys56g/bin/mysqld(_Z21mysql_execute_commandP3THD+0x26bb)[0x71b0fb]
/soft/mys56g/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x33b)[0x71ee1b]
/soft/mys56g/bin/mysqld[0x71f006]
/soft/mys56g/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x157c)[0x720e1c]
/soft/mys56g/bin/mysqld(_Z10do_commandP3THD+0x1c3)[0x722863]
/soft/mys56g/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x29d)[0x6e504d]
/soft/mys56g/bin/mysqld(handle_one_connection+0x42)[0x6e50f2]
/soft/mys56g/bin/mysqld(pfs_spawn_thread+0x127)[0x9d9b57]
/lib64/libpthread.so.0(+0x7806)[0x7f0a969d2806]
/lib64/libc.so.6(clone+0x6d)[0x7f0a956a167d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f09f0fc4b70): is an invalid pointer
Connection ID (thread ID): 19
Status: NOT_KILLED

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.
161220 15:56:38 mysqld_safe Number of processes running now: 0
161220 15:56:38 mysqld_safe WSREP: not restarting wsrep node automatically
161220 15:56:38 mysqld_safe mysqld from pid file /users/mys56g/data/yval0xm0.pid ended

Reply all
Reply to author
Forward
0 new messages