Hey Sasha, I recently wiped my 4.0.2 slave clean and installed the latest 4.0.2, built from the BK tree. Then I synced it up with a nearby slave running 3.23.47 (using rsync after I had flushed the tables on the other slave and run a "SLAVE STOP").
I started it up and it ran for about a day before it ran into a duplicate key error. The 3.23.47 slave hasn't hit the duplicate key error, nor have any of our other slaves. So it is a 4.0.2 bug of some sort. What can I do to help you debug this? It is currently "stuck". I haven't bumped the counter yet and restarted the slave. Thanks! Jeremy -- Jeremy D. Zawodny, <[EMAIL PROTECTED]> Technical Yahoo - Yahoo Finance Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 MySQL 3.23.47-max: up 78 days, processed 2,043,227,531 queries (302/sec. avg) --------------------------------------------------------------------- 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
