The mysqld process crashes after only a few queries. From this error, it's impossible to see what went wrong. Could be a bug, could be an error on our end, but there's no way to tell.
Setup:
3 - node cluster (test setup)
All on virtual machines 2 CPU / 2 GB (node3, 4 & 5)
All InnoDB
Relevant my.cnf parts: (taken from node3)
Crash happens also when running only 1 node
Percona Xtradb cluster Version 5.5.28
*no* messages of any importance before first message in trace below
Information about "no such a transition COMMITTING -> REPLICATING" nowhere to be found (manual, forum, documentation, google) but that could also be a lack of searching skills on my end.
121210 9:52:52 [ERROR] WSREP: FSM: no such a transition COMMITTING -> REPLICATING
08:52:52 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/
key_buffer_size=33554432
read_buffer_size=131072
max_used_connections=7
max_threads=200
thread_count=6
connection_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 470497 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x520a080
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 = 7f802ede8e20 thread_stack 0x40000
mysqld(my_print_stacktrace+0x2e)[0x7cd73e]
mysqld(handle_fatal_signal+0x481)[0x6b1681]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f802e027cb0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f802dc8f425]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7f802dc92b8b]
/usr/lib/libgalera_smm.so(_ZN6galera3FSMINS_9TrxHandle5StateENS1_10TransitionENS_10EmptyGuardENS_11EmptyActionEE8shift_toES2_+0x180)[0x7f802c799070]
/usr/lib/libgalera_smm.so(_ZN6galera13ReplicatorSMM9replicateEPNS_9TrxHandleE+0xc5)[0x7f802c78efb5]
/usr/lib/libgalera_smm.so(galera_pre_commit+0xb0)[0x7f802c7a1680]
mysqld(_Z22wsrep_run_wsrep_commitP3THDP10handlertonb+0x753)[0x667c63]
mysqld[0x6689fb]
mysqld(_Z15ha_commit_transP3THDb+0x13b)[0x6b42eb]
mysqld(_Z17trans_commit_stmtP3THD+0x25)[0x65d515]
mysqld(_Z21mysql_execute_commandP3THD+0x63c)[0x5ac45c]
mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x2d1)[0x5b29f1]
mysqld[0x5b2b62]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x16b9)[0x5b4e79]
mysqld(_Z10do_commandP3THD+0x171)[0x5b5521]
mysqld(_Z24do_handle_one_connectionP3THD+0x180)[0x64fcd0]
mysqld(handle_one_connection+0x51)[0x64fe91]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f802e01fe9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f802dd4ccbd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f7f90004c50): is an invalid pointer
Connection ID (thread ID): 44
Status: NOT_KILLED
The mysqld process crashes after only a few queries. From this error, it's impossible to see what went wrong. Could be a bug, could be an error on our end, but there's no way to tell.
Setup:
3 - node cluster (test setup)
All on virtual machines 2 CPU / 2 GB (node3, 4 & 5)
All InnoDB
Relevant my.cnf parts: (taken from node3)
------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ----- n_cache = 4096
# CACHES AND LIMITS #
tmp_table_size = 32M
max_heap_table_size = 32M
query_cache_type = 0
query_cache_size = 0
max_connections = 200
thread_cache_size = 20
open_files_limit = 65535
table_definitio
table_open_cache = 4096
# INNODB # log_files_ in_group = 2 log_file_ size = 128M flush_log_ at_trx_ commit = 2 file_per_ table = 1 buffer_ pool_size = 1488M
innodb_flush_method = O_DIRECT
innodb_
innodb_
innodb_
innodb_
innodb_
server_id=1 address= "gcomm: //node4, node5" /usr/lib/ libgalera_ smm.so options = "gmcast. listen_ addr=tcp: //node3; sst.recv_ addr=node3; evs.keepalive_ period = PT3S; evs.inactive_ check_period = PT10S; evs.suspect_timeout = PT30S; evs.inactive_ timeout = PT1M; evs.install_timeout = PT1M" threads= 2 name=** removed* * method= xtrabackup auth=root: **removed* * name=node3 incoming_ address= "node3: 4567" address= "node3" locks_unsafe_ for_binlog= 1 autoinc_ lock_mode= 2 ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- -----
wsrep_cluster_
wsrep_provider=
wsrep_provider_
wsrep_slave_
wsrep_cluster_
wsrep_sst_
wsrep_sst_
wsrep_node_
wsrep_node_
wsrep_node_
innodb_
innodb_
-------
Crash happens also when running only 1 node
Percona Xtradb cluster Version 5.5.28
*no* messages of any importance before first message in trace below
Information about "no such a transition COMMITTING -> REPLICATING" nowhere to be found (manual, forum, documentation, google) but that could also be a lack of searching skills on my end.
======= ======= ======= ======= ======= ======= ======= ======= ======= ===
121210 9:52:52 [ERROR] WSREP: FSM: no such a transition COMMITTING -> REPLICATING bugs.percona. com/
08:52:52 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.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_ size=33554432 size=131072 connections= 7 size)*max_ threads = 470497 K bytes of memory
read_buffer_
max_used_
max_threads=200
thread_count=6
connection_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x520a080 my_print_ stacktrace+ 0x2e)[0x7cd73e] handle_ fatal_signal+ 0x481)[ 0x6b1681] 64-linux- gnu/libpthread. so.0(+0xfcb0) [0x7f802e027cb0 ] 64-linux- gnu/libc. so.6(gsignal+ 0x35)[0x7f802dc 8f425] 64-linux- gnu/libc. so.6(abort+ 0x17b)[ 0x7f802dc92b8b] libgalera_ smm.so( _ZN6galera3FSMI NS_9TrxHandle5S tateENS1_ 10TransitionENS _10EmptyGuardEN S_11EmptyAction EE8shift_ toES2_+ 0x180)[ 0x7f802c799070] libgalera_ smm.so( _ZN6galera13Rep licatorSMM9repl icateEPNS_ 9TrxHandleE+ 0xc5)[0x7f802c7 8efb5] libgalera_ smm.so( galera_ pre_commit+ 0xb0)[0x7f802c7 a1680] _Z22wsrep_ run_wsrep_ commitP3THDP10h andlertonb+ 0x753)[ 0x667c63] _Z15ha_ commit_ transP3THDb+ 0x13b)[ 0x6b42eb] _Z17trans_ commit_ stmtP3THD+ 0x25)[0x65d515] _Z21mysql_ execute_ commandP3THD+ 0x63c)[ 0x5ac45c] _Z11mysql_ parseP3THDPcjP1 2Parser_ state+0x2d1) [0x5b29f1] _Z16dispatch_ command19enum_ server_ commandP3THDPcj +0x16b9) [0x5b4e79] _Z10do_ commandP3THD+ 0x171)[ 0x5b5521] _Z24do_ handle_ one_connectionP 3THD+0x180) [0x64fcd0] handle_ one_connection+ 0x51)[0x64fe91] 64-linux- gnu/libpthread. so.0(+0x7e9a) [0x7f802e01fe9a ] 64-linux- gnu/libc. so.6(clone+ 0x6d)[0x7f802dd 4ccbd]
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 = 7f802ede8e20 thread_stack 0x40000
mysqld(
mysqld(
/lib/x86_
/lib/x86_
/lib/x86_
/usr/lib/
/usr/lib/
/usr/lib/
mysqld(
mysqld[0x6689fb]
mysqld(
mysqld(
mysqld(
mysqld(
mysqld[0x5b2b62]
mysqld(
mysqld(
mysqld(
mysqld(
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f7f90004c50): is an invalid pointer
Connection ID (thread ID): 44
Status: NOT_KILLED
======= ======= ======= ======= ======= ======= ======= ======= ======= ===