I am running a simple master -> slave replication to just a single node. I did an update to an application which added in some triggers and then attempted to start replication back up with taking a copy from the master with innobackupex, applied the logs, and then copied it over and set it up. Replication will run for a little bit, catching up, but before too long it will crash bringing down the slave database service.
The error log is as follows that relates to the crash:
130526 12:29:21 InnoDB: Assertion failure in thread 140087775872768 in file btr0cur.c line 363
InnoDB: Failing assertion: btr_page_get_next(get_block->frame, mtr) == page_get_page_no(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to [URL=“http://bugs.mysql.com”]http://bugs.mysql.com[/URL=“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: about forcing recovery.
17:29:21 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 Server better by reporting any
bugs at [URL=“http://bugs.percona.com/"]http://bugs.percona.com/[/URL="http://bugs.percona.com/”]
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1564548 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
stack_bottom = 0 thread_stack 0x40000
You may download the Percona Server operations manual by visiting
[URL=“http://www.percona.com/software/percona-server/"]http://www.percona.com/software/percona-server/[/URL="http://www.percona.com/software/percona-server/”]. You may find information
in the manual which will help you identify the cause of the crash.
Anyone have any thoughts?