We have setup Percona XtraDB with Galera (5.5.29) and InnoDb on 3 CentOS 6.3 virtual servers. We have also setup HaProxy on a 4th CentOS 6.3 Virtual server. We are running a script for testing the configuration the Creates a table, inserts a record, selects the records, updates the record, selects the records and deletes the record and a final select on the record. We run this in a loop for 1000 iterations and we run multiple instances (x5) to ensure that all the nodes of the cluster are getting hit via HaProxy. After roughly 5,000 runs of the query one node consistently fails with a signal 11 error. Here is the stack trace:
[begin stack trace]
19:22:56 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 … [ link to bug . percona . com]
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 362577 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.
Thread pointer: 0xffffffffa64008a0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
stack_bottom = ffffffff9705a36c thread_stack 0x30000
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 2
You may download the Percona Server operations manual by visiting
[link to percona server]. You may find information
in the manual which will help you identify the cause of the crash.
[end stack trace]
Any help is appreciated.