From: Rick James
Date: February 14 2013 10:46pm
Subject: RE: slave replication with lots of 'duplicate entry' errors
List-Archive: http://lists.mysql.com/mysql/228963
Message-Id: <582AFBFC517D194489EF570FE21694CF13628F26@GQ1-EX10-MB03.y.corp.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

> Is it in read only mode?
Furthermore, are all users logging in as non-SUPER users?  Note:  root bypa=
sses the readonly flag!

> -----Original Message-----
> From: Manuel Arostegui [mailto:manuel@stripped]
> Sent: Thursday, February 14, 2013 1:55 PM
> To: Robert Citek
> Cc: mysql
> Subject: Re: slave replication with lots of 'duplicate entry' errors
>=20
> 2013/2/13 Robert Citek <robert.citek@stripped>
>=20
> > On Wed, Feb 13, 2013 at 8:59 AM, Robert Citek
> <robert.citek@stripped>
> > wrote:
> > > Any other possibilities?  Do other scenarios become likely if there
> > > are two or more tables?
> > >
> > > Of those, which are the most likely?
> >
> > [from off-list responder]:
> > > Other possibility: The replication is reading from master not from
> > > the
> > point when the dump was done, but some time before and is fetching
> > insert statements which are already in the dump.
> >
> > To prevent that I used the coordinates in the dump file included with
> > --master-data=3D2.  Could the coordinates still be off?
>=20
>=20
> Hello,
>=20
> Are you sure nothing is getting inserted directly into the slave? Is it
> in read only mode?
> If you're starting replication using the values provided by --master-
> data=3D2 (which should be something like):
>=20
>  -- Position to start replication or point-in-time recovery from
>=20
> -- CHANGE MASTER TO MASTER_LOG_FILE=3D'mysql-bin.000974',
> MASTER_LOG_POS=3D240814775;
>=20
> And if you're using the right IP, there's no reason to have duplicate
> entries unless someone is writing directly into the slave.
>=20
> Manuel.