Similar bug with 5.6.22-72.0-56-log Percona XtraDB 3 node Cluster.
That issue brought all three nodes down.
The error posted below. Will provide my.cnf if needed.
Please comment on where to look next , as the error log does not exactly provide more details.
Thank you in advance,
EC
**************
2016-08-31 21:29:02 7f8c78271700 InnoDB: Assertion failure in thread 140241287976704 in file rem0rec.cc line 580
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2016-08-31 21:29:02 27913 [Note] WSREP: cleanup transaction for LOCAL_STATE: SELECT option_value FROM dma_options WHERE option_name = 'featured-content' LIMIT 1
2016-08-31 21:29:02 27913 [Note] WSREP: cleanup transaction for LOCAL_STATE: SET autocommit=1
04:29:02 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 XtraDB Cluster better by reporting any
bugs at https://bugs.launchpad.net/percona-xtradb-cluster
key_buffer_size=536870912
read_buffer_size=131072
max_used_connections=1501
max_threads=362
thread_count=85
connection_count=82
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3545279 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x10f0bed0
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 = 7f8c78270d38 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8fa965]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x665644]
/lib64/libpthread.so.0(+0xf7e0)[0x7f8cb72b27e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f8cb56fb625]
/lib64/libc.so.6(abort+0x175)[0x7f8cb56fce05]
/usr/sbin/mysqld[0x98f8bf]
/usr/sbin/mysqld(_Z25wsrep_rec_get_foreign_keyPhPmPKhP12dict_index_tS4_m+0x72)[0x98fed2]
/usr/sbin/mysqld(_Z24wsrep_append_foreign_keyP5trx_tP14dict_foreign_tPKhP12dict_index_tmm+0x3a6)[0x914616]
/usr/sbin/mysqld[0x99fac3]
/usr/sbin/mysqld[0x9a34e2]
/usr/sbin/mysqld[0x9cb7de]
/usr/sbin/mysqld[0x9cc159]
/usr/sbin/mysqld[0x9cd781]
/usr/sbin/mysqld[0x9abdd0]
/usr/sbin/mysqld[0x99fd57]
/usr/sbin/mysqld[0x9a34e2]
/usr/sbin/mysqld[0x9cb7de]
/usr/sbin/mysqld[0x9cc159]
/usr/sbin/mysqld[0x9cd781]
/usr/sbin/mysqld[0x9b0aeb]
/usr/sbin/mysqld[0x91a53f]
/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0xac)[0x5a95ac]
/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyy+0xd5c)[0x8407bc]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x20a7)[0x6ebf07]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x658)[0x6f0958]
/usr/sbin/mysqld[0x6f0acd]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x19d5)[0x6f2de5]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x22b)[0x6f42cb]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x6bc52f]
/usr/sbin/mysqld(handle_one_connection+0x47)[0x6bc717]
/usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0xaf611a]
/lib64/libpthread.so.0(+0x7aa1)[0x7f8cb72aaaa1]
/lib64/libc.so.6(clone+0x6d)[0x7f8cb57b193d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f89e9126c00): is an invalid pointer
Connection ID (thread ID): 45301651
Status: NOT_KILLED
You may download the Percona XtraDB Cluster operations manual by visiting http://www.percona.com/software/percona-xtradb-cluster/. You may find information
in the manual which will help you identify the cause of the crash.
160831 21:29:04 mysqld_safe Number of processes running now: 0
160831 21:29:04 mysqld_safe WSREP: not restarting wsrep node automatically
160831 21:29:04 mysqld_safe mysqld from pid file /var/lib/mysql/mysqld.pid ended
Similar bug with 5.6.22-72.0-56-log Percona XtraDB 3 node Cluster.
That issue brought all three nodes down.
The error posted below. Will provide my.cnf if needed.
Please comment on where to look next , as the error log does not exactly provide more details.
Thank you in advance,
EC
************** bugs.mysql. com. dev.mysql. com/doc/ refman/ 5.6/en/ forcing- innodb- recovery. html /bugs.launchpad .net/percona- xtradb- cluster
2016-08-31 21:29:02 7f8c78271700 InnoDB: Assertion failure in thread 140241287976704 in file rem0rec.cc line 580
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
2016-08-31 21:29:02 27913 [Note] WSREP: cleanup transaction for LOCAL_STATE: SELECT option_value FROM dma_options WHERE option_name = 'featured-content' LIMIT 1
2016-08-31 21:29:02 27913 [Note] WSREP: cleanup transaction for LOCAL_STATE: SET autocommit=1
04:29:02 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 XtraDB Cluster better by reporting any
bugs at https:/
key_buffer_ size=536870912 size=131072 connections= 1501 size)*max_ threads = 3545279 K bytes of memory
read_buffer_
max_used_
max_threads=362
thread_count=85
connection_count=82
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: 0x10f0bed0 mysqld( my_print_ stacktrace+ 0x35)[0x8fa965] mysqld( handle_ fatal_signal+ 0x4b4)[ 0x665644] libpthread. so.0(+0xf7e0) [0x7f8cb72b27e0 ] libc.so. 6(gsignal+ 0x35)[0x7f8cb56 fb625] libc.so. 6(abort+ 0x175)[ 0x7f8cb56fce05] mysqld[ 0x98f8bf] mysqld( _Z25wsrep_ rec_get_ foreign_ keyPhPmPKhP12di ct_index_ tS4_m+0x72) [0x98fed2] mysqld( _Z24wsrep_ append_ foreign_ keyP5trx_ tP14dict_ foreign_ tPKhP12dict_ index_tmm+ 0x3a6)[ 0x914616] mysqld[ 0x99fac3] mysqld[ 0x9a34e2] mysqld[ 0x9cb7de] mysqld[ 0x9cc159] mysqld[ 0x9cd781] mysqld[ 0x9abdd0] mysqld[ 0x99fd57] mysqld[ 0x9a34e2] mysqld[ 0x9cb7de] mysqld[ 0x9cc159] mysqld[ 0x9cd781] mysqld[ 0x9b0aeb] mysqld[ 0x91a53f] mysqld( _ZN7handler13ha _delete_ rowEPKh+ 0xac)[0x5a95ac] mysqld( _Z12mysql_ deleteP3THDP10T ABLE_LISTP4Item P10SQL_ I_ListI8st_ orderEyy+ 0xd5c)[ 0x8407bc] mysqld( _Z21mysql_ execute_ commandP3THD+ 0x20a7) [0x6ebf07] mysqld( _Z11mysql_ parseP3THDPcjP1 2Parser_ state+0x658) [0x6f0958] mysqld[ 0x6f0acd] mysqld( _Z16dispatch_ command19enum_ server_ commandP3THDPcj +0x19d5) [0x6f2de5] mysqld( _Z10do_ commandP3THD+ 0x22b)[ 0x6f42cb] mysqld( _Z24do_ handle_ one_connectionP 3THD+0x17f) [0x6bc52f] mysqld( handle_ one_connection+ 0x47)[0x6bc717] mysqld( pfs_spawn_ thread+ 0x12a)[ 0xaf611a] libpthread. so.0(+0x7aa1) [0x7f8cb72aaaa1 ] libc.so. 6(clone+ 0x6d)[0x7f8cb57 b193d]
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 = 7f8c78270d38 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f89e9126c00): is an invalid pointer
Connection ID (thread ID): 45301651
Status: NOT_KILLED
You may download the Percona XtraDB Cluster operations manual by visiting www.percona. com/software/ percona- xtradb- cluster/. You may find information mysql/mysqld. pid ended
http://
in the manual which will help you identify the cause of the crash.
160831 21:29:04 mysqld_safe Number of processes running now: 0
160831 21:29:04 mysqld_safe WSREP: not restarting wsrep node automatically
160831 21:29:04 mysqld_safe mysqld from pid file /var/lib/