Description:
100107 23:22:22 [Note] Semi-sync replication switched ON with slave (server_id: 2) at (master-bin.000001, 26148710)
100107 23:22:30 [ERROR] ActiveTranx:insert_tranx_node: binlog write out-of-order, tail (master-bin.000001, 39318405), new node (master-bin.00
0001, 39318405)
100107 23:22:30 [Warning] Semi-sync failed to insert tranx_node for binlog file: master-bin.000001, position: 39318405
100107 23:22:30 [Note] Semi-sync replication switched OFF.
100107 23:22:30 [Note] Semi-sync replication switched ON with slave (server_id: 2) at (master-bin.000001, 39323595)
100107 23:22:30 [ERROR] ActiveTranx:insert_tranx_node: binlog write out-of-order, tail (master-b<E8>^X^C<B4><AA>*, 46912652909181), new node
(master-bin.000001, 39330777)
100107 23:22:30 [Warning] Semi-sync failed to insert tranx_node for binlog file: master-bin.000001, position: 39330777
100107 23:22:30 [Note] Semi-sync replication switched OFF.
100107 23:22:30 [Note] Semi-sync replication switched ON with slave (server_id: 2) at (master-bin.000001, 39331243)
100107 23:22:30 - 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.
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=1048576
read_buffer_size=131072
max_used_connections=6
max_threads=151
threads_connected=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 60561 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x1583d190
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 = 0x461d1100 thread_stack 0x40000
bin/mysqld(my_print_stacktrace+0x2e)[0x8bcc2e]
bin/mysqld(handle_segfault+0x322)[0x5cc032]
/lib64/libpthread.so.0[0x33a8c0de70]
lib/plugin/semisync_master.so(_ZN11ActiveTranx24clear_active_tranx_nodesEPKcy+0x68)[0x2aaaab976488]
lib/plugin/semisync_master.so(_ZN18ReplSemiSyncMaster17reportReplyBinlogEjPKcy+0xd8)[0x2aaaab9775e8]
lib/plugin/semisync_master.so(_ZN18ReplSemiSyncMaster14readSlaveReplyEP6st_netjPKc+0x1f2)[0x2aaaab977912]
lib/plugin/semisync_master.so(_Z26repl_semi_after_send_eventP21Binlog_transmit_paramPKcm+0x77)[0x2aaaab977ee7]
bin/mysqld(_ZN24Binlog_transmit_delegate16after_send_eventEP3THDtP6String+0xe8)[0x759938]
bin/mysqld(_Z17mysql_binlog_sendP3THDPcyt+0x7a5)[0x714fe5]
bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x76e)[0x5e2dae]
bin/mysqld(_Z10do_commandP3THD+0xe3)[0x5e3e73]
bin/mysqld(handle_one_connection+0x23e)[0x5d616e]
/lib64/libpthread.so.0[0x33a8c062f7]
/lib64/libc.so.6(clone+0x6d)[0x33a80d1b6d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is an invalid pointer
thd->thread_id=2
thd->killed=NOT_KILLED
How to repeat:
- unpack the attached archive in <mysql-basedir>/mysql-test. It should create
'stress_test_basedir' folder;
- run as
perl ./stress_test_basedir/run.pl
Notes:
run.pl is a wrapper for MTR to start server, and mysql-stress-test to run a 5-thread stress test.
For mysql-stress-test you need to have perl with threads on the top of your path (or please modify run.pl to call mysql-stress-test.pl with the right perl).
The screen output should say 'Waiting for server(s) to exit...' for a few seconds (sleep time for the server to start), and then start rapidly producing lines like
test_loop[0:0 0:377]: TID 2 test: 'stress2' Errors: No Errors. Test Passed OK
test_loop[0:0 0:378]: TID 1 test: 'stress1' Errors: No Errors. Test Passed OK
When/if the problem is hit, the output says something like
test_loop[0:0 0:7]: TID 2 test: 'stress1' Errors: Severity S1: 15 (thread aborting)
and the test exits
If the server does not start fast enough, the test might abort immediately; in this case please increase sleep time in run.pl.
