Short Version: Is replication from 5.5 master to a 5.1 slave possible?
Long Version: We did a large scale upgrade from 5.0 to 5.5. It was a long process if dumping the 400gb dbs and importing them into 5.5.
5.5 replication seems to be completely broken. The masters consistently hang, the slaves keep dis/reconnecting and leaving stale binlog_dump connections (visible from show processlist). The master hangs on shutdown until I have to kill when shutdown "gives up" after an hour. Lastly it gets this type error daily "110423 13:55:48 [ERROR] Slave SQL: Could not execute Delete_rows event on table prod.site_iplist; Can't find record in 'site_iplist', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log mysql-bin.000385, end_log_pos 65644796, Error_code: 1032" which is a bug that is will be fixed in 5.5.12.
This has been very disappointing, as our 5.0 setup ran fine for 3 years.
Anyhow, I am looking to move to 5.1.56 (which has at least 56 updates to a stable product). The problem is that all my databases are 5.5 now.
Is it possible to have a 5.5 master and a 5.1 slave? The migration process being to import the db into 5.1 and then enable replication, fail everyone over to 5.1 once it is synced up, and then downgrade all the other 5.5 servers while everyone is on the 5.1 db.
Will 5.5 master --> 5.1 slave work at all? If so, will it work with the current MIXED mode replication? Would I have to change that to be statement only?