Jeremy Zawodny wrote:
On Mon, Nov 18, 2002 at 05:41:51PM +0100, Stefan Bohm wrote:
>when upgrading the master in a master slave setup from 3.23.x to
>4.0.x or downgrading back to 3.23.x the binlog seems to be corrupt
>for the slaves. I get error messages like "binlog truncated" or
>'unexpected success or fatal error' on query ''
>
>I always have to copy the whole DB to the slave and start the
>replication all over.
>
>Am I doing something wrong?
The binlog format has changed, yes.
I suggest that next time you make sure your slaves are up-to-date and
flush the binlog on the master. That'll allow it to start from a
clean slate after the upgrade.
Also, what version are your slaves running? I've seen 4.x slaves
replicate from a 3.23 master, but not the reverse...
Jeremy
Hi Jeremy,
I'm currently running 4.0.5 on the slaves.
Can you tell me the correct way to upgrade a master while the slaves are
up and running?
Do I have to stop replication on the slaves first and flush the logs on the
master before shutting him down fpr upgrade?
Thank you for your assistance
Stefan
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
