That got me greping through my Master's log and I came accross the following :

Error reading packet from server: log event entry exceeded max_allowed_packet - increase max_allowed_packet on master (server_errno=65535)

This seems to have happened in the date ranges where replication was failing. I cant confirm it is related but is it possible this would cause replication to fail on the server ?

Also a new table is created every day therefore a single failure cant have been the reason for replication failure over a period of time.

It also brings me to a critical question what do I set as the max_allowed_packet so that I will successfully save all updates to a TEXT field? TEXT fields dont have a size limit so how do I make sure I will never see this error ?



Mithun

Jeremy Zawodny wrote:


I can successfully run the SQL on the slave manually and it obviously has run successfully on the master.


Why is that obvious?

It's telling you that the slave expected to get an error but didn't.
Those expectations come from the master's binlog.

I'd repair the table on the master, since it's likely in some sort of
trouble.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to