I was restarting a node with a peer and it needed to use xtrabackup. It finished entirely and the other node started the restore… The node which I was restoring from crashed suddenly with the following:
06:59:00 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 = 1860912 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.
Thread pointer: 0x168d2e10
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 = 7f822c442e48 thread_stack 0x40000
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f8238004e50): is an invalid pointer
Connection ID (thread ID): 50
You may download the Percona Server operations manual by visiting
. You may find information
in the manual which will help you identify the cause of the crash.
This is obviously pretty bad. I am restarting the node now, but why did this happen in the first place?