Hello.
Not enough information to make a conclusion. Use SHOW SLAVE STATUS and information from the binary logs to determine the problem. See: http://dev.mysql.com/doc/mysql/en/replication-problems.html David Lloyd <[EMAIL PROTECTED]> wrote: > > Hi There, > > > I have a replication setup on my local network (so any updates can be > transported at around ethernet speed). > > Here's the behaviour I see: > > * MySQL Master > > - I do a whole slew of drop table and create tables > > * MySQL Slave > > - It doesn't pick them up > > ... until ... > > - I restart the slave > > It doesn't appear to have a problem with a single database table being > dropped, only when I drop a whole heap at once [I'm replacing the > underlying scheme with a heap of drop table ifs followed by create table]. > > I'm running the official "mysql-4.1.10" Apple binaries. One on my OS X > server [which is the master] and another on OS X [not server] [which is > the slave]. > > Anywhere I can work out what might be happening or why the updates are > being sent through? > > DSL > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
