Could there have been a deadlock on the slave and the replication item
was the loser in the duel?
Rick James
MySQL Geeks - Consulting & Review
> -----Original Message-----
> From: Jesse [mailto:jc@stripped]
> Sent: Tuesday, September 30, 2008 10:11 AM
> To: replication@stripped
> Subject: Replication Stopping (foreign key issue)
>
> Replication has come to a halt on my slave machine because of
> a foreign key
> constraint issue. It was attempting to add a child record
> for a parent
> record that is not present. After checking it, starting with that
> particular missing parent record, there are no more below
> that area. My
> question is this. If it's present on the master, why
> wouldn't it be present
> on the slave before the child record would have been added?
> I did not
> receive such an error on the master server?? I could
> probably add the
> missing master record, but the problem is that this will
> occur again. It's
> happened about 3 times now. Does anyone have any suggestions?
>
> Thanks,
> Jesse
>
>
> --
> MySQL Replication Mailing List
> For list archives: http://lists.mysql.com/replication
> To unsubscribe:
> http://lists.mysql.com/replication?unsub=1
>
>
