Thanks & Kind Regards,
> TRIMURTHY
>
>
>
>
>
> From: "Mike Franon"
> Sent: Thursday, February 21, 2013 11:43 PM
> To: "Reindl Harald"
> Subject: Re: replication fails after upgrade to 5.6
>
> Unfortunately that is not
13 10:30 AM
>> To: mysql@lists.mysql.com
>> Subject: Re: replication fails after upgrade to 5.6
>>
>> Am 21.02.2013 19:11, schrieb Mike Franon:
>>> Is the only way to really fix this is to upgrade master? I thought
>>> you can replicate from master -> s
It is safer to have the Slave be a newer version.
> -Original Message-
> From: Reindl Harald [mailto:h.rei...@thelounge.net]
> Sent: Thursday, February 21, 2013 10:30 AM
> To: mysql@lists.mysql.com
> Subject: Re: replication fails after upgrade to 5.6
>
>
>
Am 21.02.2013 19:11, schrieb Mike Franon:
> Is the only way to really fix this is to upgrade master? I thought
> you can replicate from master -> slave if version is higher on slave,
> just not the other way around?
normally no
but take a look at the changelogs of myslq in the last years
80 ou
Unfortunately that is not possible at the moment, I have 6 slaves off
the one master, also I want to test it as much as possible before
upgrading the master.
Is the only way to really fix this is to upgrade master? I thought
you can replicate from master -> slave if version is higher on slave,
ju
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
bo
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
I keep getting Error 1062, Duplicate Entry for key
I get no errors when I do a mysql_upgrade, all comes back ok.
I was
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 working
for about 10 minutes and then got the following error:
[ERROR] Slave SQL: Error 'Duplicate entry 'data' for key 'PRIMARY'' on
query. Default database
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 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 t
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 working
> for about 10 minutes and then got the following error:
>
> [ERROR] Slave SQL: Error 'Duplicate en
10 matches
Mail list logo
