- Mensaje original -
De: Manuel Arostegui
Para: Miguel Gonzalez
CC: mysql@lists.mysql.com
Enviado: Jueves 21 de marzo de 2013 9:17
Asunto: Re: Promoting MySQL 5.5 slave to master
2013/3/21 Miguel Gonzalez
>
>
>
> Can you elaborate about this? I thought that once y
>[AM] If you've the option to use MySQL 5.6 then managing replication is a lot
>simpler and more reliable...
>http://www.clusterdb.com/mysql-replication/mysql-5-6-ga-replication-enhancements/
>MySQL 5.6 Failing over is described in section 5 of
>http://www.mysql.com/why-mysql/white-papers/my
> -Original Message-
> From: Miguel Gonzalez [mailto:miguel_3_gonza...@yahoo.es]
> Sent: 21 March 2013 08:29
> To: Manuel Arostegui
> Cc: mysql@lists.mysql.com
> Subject: Re: Promoting MySQL 5.5 slave to master
>
>
>
>
>
> - Mensaje original
2013/3/21 Miguel Gonzalez
>
>
>
> Can you elaborate about this? I thought that once you fixed the issues in
> the master server you needed to set it as slave of the new promoted master
> server, and do the other way round.
>
>
That's why you might want to have master-master replication to avoid t
2013/3/21 Miguel González Castaños
> Dear all,
>
>I have a pretty simple setup. A LAMP server in production and a
> failover LAMP server in case the main server is down.
>
>I have been searching around to find out a clear answer of how to
> proceed when you need to promote a MySQL 5.5 sla
Dear all,
I have a pretty simple setup. A LAMP server in production and a
failover LAMP server in case the main server is down.
I have been searching around to find out a clear answer of how to
proceed when you need to promote a MySQL 5.5 slave server when the
master (also 5.5) has cra
