Node with galera 2.x crashes on JOIN

Bug #890973 reported by Vadim Tkachenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Galera
Fix Released
High
Alex Yurchenko

Bug Description

I am joining Node 5.5 with galera 2.x
to cluster with one full node and with garbd

I am getting crash:

111115 20:40:41 [Note] Event Scheduler: Loaded 0 events
111115 20:40:41 [Note] WSREP: Signalling provider to continue.
111115 20:40:41 [Note] WSREP: Received SST: 7983c837-1004-11e1-0800-93f2ad9a51bb:349
111115 20:40:41 [Note] WSREP: SST finished: 7983c837-1004-11e1-0800-93f2ad9a51bb:349
terminate called after throwing an instance of 'gu::Exception'
  what(): URI '' has empty scheme: 22 (Invalid argument)
         at galerautils/src/gu_uri.cpp:parse():145
[New Thread 0x7fefa08d5700 (LWP 23809)]
111115 20:40:41 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.17-wsrep_22.3dev' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffd6ffcd700 (LWP 21887)]
0x0000003034432a45 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install boost-program-options-1.41.0-11.el6.x86_64 glibc-2.12-1.25.el6.x86_64 keyutils-libs-1.4-1.el6.x86_64 krb5-libs-1.9-9.el6.x86_64 libaio-0.3.107-10.el6.x86_64 libcom_err-1.41.12-7.el6.x86_64 libgcc-4.4.5-6.el6.x86_64 libselinux-2.0.94-5.el6.x86_64 libstdc++-4.4.5-6.el6.x86_64 nss-softokn-freebl-3.12.9-3.el6.x86_64 openssl-1.0.0-10.el6.x86_64 zlib-1.2.3-25.el6.x86_64
(gdb) bt
#0 0x0000003034432a45 in raise () from /lib64/libc.so.6
#1 0x0000003034434225 in abort () from /lib64/libc.so.6
#2 0x000000303a8bea7d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6
#3 0x000000303a8bcc06 in ?? () from /usr/lib64/libstdc++.so.6
#4 0x000000303a8bcc33 in std::terminate() () from /usr/lib64/libstdc++.so.6
#5 0x000000303a8bcc46 in ?? () from /usr/lib64/libstdc++.so.6
#6 0x000000303a8bc2d3 in __cxa_call_unexpected () from /usr/lib64/libstdc++.so.6
#7 0x00007ffff718277d in galera::ReplicatorSMM::request_state_transfer (this=<value optimized out>, recv_ctx=0x7ffd64000990,
    group_uuid=<value optimized out>, group_seqno=<value optimized out>, sst_req=<value optimized out>,
    sst_req_len=<value optimized out>) at galera/src/replicator_str.cpp:550
#8 0x00007ffff7173161 in galera::ReplicatorSMM::process_conf_change (this=0x1071ba0, recv_ctx=0x7ffd64000990, view_info=...,
    repl_proto=1, next_state=galera::Replicator::S_CONNECTED, seqno_l=<value optimized out>) at galera/src/replicator_smm.cpp:1128
#9 0x00007ffff71571f6 in galera::GcsActionSource::dispatch (this=0x10720a0, recv_ctx=0x7ffd64000990, act=<value optimized out>)
    at galera/src/gcs_action_source.cpp:132
#10 0x00007ffff71574a8 in galera::GcsActionSource::process (this=0x10720a0, recv_ctx=0x7ffd64000990)
    at galera/src/gcs_action_source.cpp:162
#11 0x00007ffff717266d in galera::ReplicatorSMM::async_recv (this=0x1071ba0, recv_ctx=0x7ffd64000990)
    at galera/src/replicator_smm.cpp:351
#12 0x00007ffff7186c63 in galera_recv (gh=<value optimized out>, recv_ctx=<value optimized out>)
    at galera/src/wsrep_provider.cpp:196
#13 0x000000000057be23 in wsrep_replication_process(THD*) ()
#14 0x000000000050265f in start_wsrep_THD ()
#15 0x00000030348077e1 in start_thread () from /lib64/libpthread.so.0
#16 0x00000030344e68ed in clone () from /lib64/libc.so.6
(gdb)

Related branches

Revision history for this message
Vadim Tkachenko (vadim-tk) wrote :

This happens when one of nodes is garbd ( from galera/1.x).

Without garbd I do not have the crash.

affects: codership-mysql → galera
Changed in galera:
assignee: nobody → Alex Yurchenko (ayurchen)
importance: Undecided → High
milestone: none → 22.2.0beta
status: New → In Progress
Revision history for this message
Alex Yurchenko (ayurchen) wrote :

Consider fixed at least in r103.

Changed in galera:
status: In Progress → Fix Committed
Changed in galera:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.