MySQL crashes when replicate_ignore_table is set

Bug #1058418 reported by Anil Dasari
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
New
Undecided
Unassigned

Bug Description

Version: Percona-Server-55-5.5.27-rel28.1.296.rhel5, installed from x86_64 rpm.
OS: CentOS 5

Problem:
I've upgraded from Percona-Server-5.1.45 to 5.5.27-28.1-log following the instructions provided in Percona documentation. mysql_upgrade was also run successfully. Server started fine. It was setup as a slave to a 5.1.45 server. After the upgrade, replication ran fine for a day. Then I added a single replicate_ignore_table entry to config file and rebooted DB. SHOW SLAVE STATUS reported the table in ignore list. But then, after I ran START SLAVE, db crashed immediately with the following error message:

- 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.

If I remove the replicate_ignore_table option, replication runs fine. If I put it back, it crashes instantly after START SLAVE. I also tried replicate_ignore_db, which seems to be fine.

Btw, replication thread was the only thread running on this server. No other connections.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.