From: Reindl Harald
Date: February 21 2013 6:03pm
Subject: Re: replication fails after upgrade to 5.6
List-Archive: http://lists.mysql.com/mysql/229028
Message-Id: <5126617E.5050003@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="----enig2FGNLLKCMVRCRSAEQQPUV"

------enig2FGNLLKCMVRCRSAEQQPUV
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

update the master ASAP in a short timeframe too
and re-init replication if needed

normally both should have exactly the same version

the slaves must be updated first because otherwise
a master may write instructions in the binlog the older
slave does not undersatdn at all, but as said normally
both should have the same version

Am 21.02.2013 18:03, schrieb Mike Franon:
> So I created a new test box on AWS, and just did one upgrade from
> 5.0.96 to 5.1, like I did before and replication will not work from a
> master with 5.0.96 to a slave with 5.1.68
>=20
> I keep getting Error 1062, Duplicate Entry for key
>=20
> I get no errors when I do a mysql_upgrade, all comes back ok.
>=20
> I was curious if anyone had any ideas?
>=20
> Thanks
>=20
> On Wed, Feb 20, 2013 at 5:51 PM, Mike Franon <kongfranon@stripped> wro=
te:
>> This is on a slave, i only upgraded on one box which is the slave i
>> have not touched master
>>
>> On Wed, Feb 20, 2013 at 5:41 PM, Reindl Harald <h.reindl@stripped=
> wrote:
>>>
>>>
>>> Am 20.02.2013 23:27, schrieb Mike Franon:
>>>> So I successfully upgraded a test db server from 5.0.96 all the way =
up to 5.6
>>>>
>>>> Replication as the slave, where the master is 5.0.96, started workin=
g
>>>> for about 10 minutes and then got the following error:
>>>>
>>>> [ERROR] Slave SQL: Error 'Duplicate entry 'data' for key 'PRIMARY'' =
on
>>>> query. Default database: 'test'. Query: 'UPDATE IGNORE , Error_code:=

>>>> 1062
>>>>
>>>> All of our other slaves on 5.0.96 are fine, so I know it has to do
>>>> with 5.6 but just not sure what, when ir an mysql_upgrade everything=

>>>> was OK
>>>
>>> did you surely upgrade and restart the slaves first?
>>>
>>> i personally would NOT go to 5.6 now
>>>
>>> it is a very young release and looking and the typical changelogs
>>> replication has always the most fixed bugs


------enig2FGNLLKCMVRCRSAEQQPUV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlEmYX4ACgkQhmBjz394Anl/1QCeKT9VhHVMYmR/mDfcD6JsxOm3
GdYAn2uh4k9IHJ+0g51wXZ+hL9+5xdkE
=zEbj
-----END PGP SIGNATURE-----

------enig2FGNLLKCMVRCRSAEQQPUV--