MySQL Bugs: #44777: chained replication problem with different mysql version

Bug #44777	chained replication problem with different mysql version
Submitted:	11 May 2009 8:27	Modified:	12 May 2009 9:45
Reporter:	Lefevre Sebastien	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S2 (Serious)
Version:		OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
Hello,
I use a mixed version mysql in chained replication:
master(A) 4.1.11 -> slave/master (B) 4.1.11 -> slave (C) 5.1.34

"log-slave-updates" is active on B and C.

Some "DELETE" queries are not replicated between the 4.1 (B) and 5.1 (C).
Queries that are not replicated include the word NOW.

example in binlog 4.1 on B: 

# at 143351312
#090510  5:10:02 server id 10  end_log_pos 143351446    Query   thread_id=235533156     exec_time=1449  error_code=0
SET TIMESTAMP=1241925002/*!*/;
DELETE FROM mydb.buy WHERE toto != 'WEB' AND DATEDIFF(NOW(), DATE(GREATEST(datestart, dateend))) > 90
/*!*/;

this query is not present in binlog C 5.1
	
Other requests are replicated.

All the tables are in MyIsam mode.
No errors in mysql.err

How to repeat:
Resetting replication does not solve the problem.

Thank you for the report.

Please provide output of SHOW SLAVE STATUS and full error log from 5.1.34 slave.

I found my problem.
I configure replication between B and C with replicate_do_db.
I saw in binlog that some queries do not use USE mydb, but "delete from mydb.mytable....". These queries are not replicated.

I closed this ticket

closed