MySQL Bugs: #65449: MySQL Replication Error

Bug #65449	MySQL Replication Error
Submitted:	29 May 2012 8:32	Modified:	30 May 2012 11:37
Reporter:	Anupam Karmarkar	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S2 (Serious)
Version:	mysql 5.5.24	OS:	Linux (CENT OS 5.5)
Assigned to:		CPU Architecture:	Any
Tags:	Replicate-do-table, replication

Description:
Hi,

I have one master and multiple slave setup in production, One of our slave requires data from master only for two tables so i have added option in configuration file replicate-do-table for these tables. For this table changes are working fine, But,
if there are any updates on procedure in any of the master databases, slave is trying to execute that in slave server, which is failing and replication is getting stuck, every time i need to set skip count and restart slave.
Please let me know how can i resolve this 
  

How to repeat:
create master slave setup, create multiple databases on master side create tables and procedures in these database,On slave side replicate only few tables from master databases using replicate-do-table option. 
On master database change procedure, verify slave slave status

Please, send my.cnf file content from master and problematic slave and typical code of procedure you create/alter on master when you get problem on this slave. The output of SHOW SLAVE STATUS when this happens may be also useful.

Master my.cnf

Attachment: Master-my.cnf (application/octet-stream, text), 1.59 KiB.

Slave my.cnf

Attachment: Slave-my.cnf (application/octet-stream, text), 1.32 KiB.

Slave error

Attachment: Slave.error (application/octet-stream, text), 2.50 KiB.

Procedure exmple

Attachment: Procedure.example (application/octet-stream, text), 500 bytes.

Please find requested files

2 Tables which are replicating on slave are not part of procedure also.

Looks similar to bug #59135

Thank you for the report.

This is actually duplicate of bug #37157 for which was considered to explain this behavior in documentation and don't fix the server.

Workaround:

replicate-do-db=XXX
replicate-ignore-table=XXX
replicate-ignore-table=XXX
...