I don't have the error anymore, but the slave will start, but when you show
slave status, it shows that there is a failure, and the failure was, a
duplicate primary key.
What i did to fix/bandaid it, was i truncated the table on the slave, and
restarted the slave again... then i did a delete on the master, where ID <
From: Johnny Withers [mailto:johnny@stripped]
Sent: March 5, 2010 1:11 PM
To: Steven Staples
Subject: Re: Master/Slave - trucate master table
Does START SLAVE fail?
If so, what is the output of SHOW SLAVE STATUS?
On Fri, Mar 5, 2010 at 10:11 AM, Steven Staples <sstaples@stripped> wrote:
> Good day everyone...
> I am working with a master/slave set up, and of course, we started it once
> the database tables were a combined size of 60gb+
> We've got it running and in sync now, (stopped the master, deleted the bin
> files, rsync'd the database tables and restarted the master) and all has
> been fine for the last week... until today.
> We stopped the mysql process on the slave, and did a backup (due to size,
> just rsync and backup the rsync) of the table files. Took about 40
> to do (still not sure why it was that long, but anyway), and then we
> restarted the slave mysql. We're getting an error now. Apparently one of
> the tables is out of sync now? What appears to have happened, is that
> the slave was down, i truncated a table on the master.
> I've read that this sometimes causes errors, is this a bug? Or a is there
> something I should do differently?
> Steven Staples
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.733 / Virus Database: 271.1.1/2711 - Release Date: 03/05/10