Crash after adding optimize settings

Bug #1200551 reported by Jérôme DENIS on 2013-07-12
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Invalid
Undecided
Unassigned

Bug Description

After adding some conf values in my.cnf, everything worked fine, but it has crashed 15 minutes after with this message :

08:26:30 UTC - 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

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

Thread pointer: 0x0
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 = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7e6045]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x6b36e4]
/lib/libpthread.so.0(+0xeff0)[0x7ff607d6aff0]
/usr/lib64/libgalera_smm.so(_ZN6gcache10RingBuffer14get_new_bufferEl+0x167)[0x7ff5fd95c6f7]
/usr/lib64/libgalera_smm.so(_ZN6gcache10RingBuffer6mallocEl+0x39)[0x7ff5fd95c919]
/usr/lib64/libgalera_smm.so(_ZN6gcache6GCache6mallocEl+0x97)[0x7ff5fd95e317]
/usr/lib64/libgalera_smm.so(gcs_defrag_handle_frag+0x92)[0x7ff5fda1bbe2]
/usr/lib64/libgalera_smm.so(gcs_core_recv+0x4a1)[0x7ff5fda21591]
/usr/lib64/libgalera_smm.so(+0x166070)[0x7ff5fda28070]
/lib/libpthread.so.0(+0x68ca)[0x7ff607d628ca]
/lib/libc.so.6(clone+0x6d)[0x7ff607003b6d]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
130712 10:26:30 mysqld_safe Number of processes running now: 0
130712 10:26:30 mysqld_safe WSREP: not restarting wsrep node automatically
130712 10:26:30 mysqld_safe mysqld from pid file /var/lib/mysql/clustersql3.pid ended

Here is my old my.cnf

[mysqld]

############################
# Configuration du cluster #
############################

server_id = 1
wsrep_provider = /usr/lib64/libgalera_smm.so
wsrep_cluster_address = gcomm://172.16.0.25,172.16.0.31
wsrep_cluster_name = ewisql
wsrep_slave_threads = 2
wsrep_sst_method = rsync
wsrep_node_name = clustersql1
wsrep_debug = OFF

#########
# MySQL #
#########

datadir = /var/lib/mysql/
binlog_format = ROW
default_storage_engine = InnoDB
log_error = /var/log/mysql/error.log
log_slow_queries = /var/log/mysql/mysql-slow.log
max_connections = 1000

##########
# InnoDB #
##########

innodb_autoinc_lock_mode = 2
innodb_locks_unsafe_for_binlog = 1
innodb_flush_log_at_trx_commit = 2
innodb_buffer_pool_size = 512M
innodb_additional_mem_pool_size = 20M

And the new version wich cause the crash :

[mysqld]

############################
# Configuration du cluster #
############################

server_id = 3
wsrep_provider = /usr/lib64/libgalera_smm.so
wsrep_cluster_address = gcomm://172.16.0.25,172.16.0.15
wsrep_cluster_name = ewisql
wsrep_slave_threads = 2
wsrep_sst_method = rsync
wsrep_node_name = clustersql3
wsrep_debug = OFF

#########
# MySQL #
#########

binlog_format = ROW
default_storage_engine = InnoDB
log_error = /var/log/mysql/error.log
log_slow_queries = /var/log/mysql/mysql-slow.log
max_connections = 1000
query_cache_size = 128M
join_buffer_size = 256K
thread_cache_size = 4

##########
# InnoDB #
##########

innodb_autoinc_lock_mode = 2
innodb_locks_unsafe_for_binlog = 1
innodb_flush_log_at_trx_commit = 2
innodb_buffer_pool_size = 1024M
innodb_additional_mem_pool_size = 20M

Kenny Gryp (gryp) wrote :

This is a PXC Related Crash

Changed in percona-server:
status: New → Invalid

@Jerome,

Can you provide the versions - Galera and PXC - with which you saw this crash?

no longer affects: percona-server
Jérôme DENIS (jerome-denis) wrote :

@raghavendra-prabhu

This my version :
mysqld Ver 5.5.29-55-log for Linux on x86_64 (Percona XtraDB Cluster (GPL), wsrep_23.7.2.r3843)

My environnement is :
Openvz on debian 6 - Ram 4Go

Thx

@Jerome,

What about the galera version?

Jérôme DENIS (jerome-denis) wrote :

@raghavendra-prabhu

How can i get galera version ?

Jérôme DENIS (jerome-denis) wrote :

@raghavendra-prabhu

Ok i found it , this is galera version 2.3(r143)

Jérôme DENIS (jerome-denis) wrote :

@raghavendra-prabhu

It was critical for us, so we've done an upgrade to galera v2.6(r152), and everything seems to be stable, pfiouuu !!

thx for your answers, i will notice here if it is really stable during this week for passing this ticket to fixed.

Jérôme DENIS (jerome-denis) wrote :

OK, upgrade fixe the problem !

@Jerome,

Thanks, marking this ticket invalid.

Changed in percona-xtradb-cluster:
status: New → Invalid

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1393

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers