In the last 1.5 weeks, we’ve started running into a very strange issue where we have 5 different slaves that will suddenly completely crash in the middle of replication. Once that happens, we can never successfully get replication going again without completely re-initializing the slave. This happens at minimum every 24 hours.
I’ve already verified that these slaves are not overloaded in the slightest. There’s plenty of free memory and CPU is no where close to being fully utilized.
Once the crash happens, MySQL will never be able to start again until it is started with “skip-slave-start”. Once the command for “start slave” is issued, the server immediately crashes. I have looked in the relay logs on the slave and in the binary logs on the master and I cannot see anything wrong at all with the queries being sent to the slave. Here are the crash details from the logs. The messages appear immediately after the slave connects to the master to start replication.
08:14:48 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
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 445843 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.
Thread pointer: 0x24622950
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 = 4bef40e8 thread_stack 0x40000
/opt/apps/ms/mysql/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE _LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xd8)[0x 567638]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2462fdb0): ▒▒▒
Connection ID (thread ID): 77