Re: [ClusterLabs] Mysql slave did not start replication after failure, and read-only IP also remained active on the much outdated slave

; To: users@clusterlabs.org >> Subject: Re: [ClusterLabs] Mysql slave did not start replication after >> failure, >> and read-only IP also remained active on the much outdated slave >> >> On 08/22/2016 07:24 AM, Attila Megyeri wrote: >>> Hi Andrei, >>

Re: [ClusterLabs] Mysql slave did not start replication after failure, and read-only IP also remained active on the much outdated slave

> > > -Original Message- > From: Andrei Borzenkov [mailto:arvidj...@gmail.com] > Sent: Monday, August 22, 2016 11:42 AM > To: Cluster Labs - All topics related to open-source clustering welcomed > <users@clusterlabs.org> > Subject: Re: [ClusterLabs] Mysql slave d

Re: [ClusterLabs] Mysql slave did not start replication after failure, and read-only IP also remained active on the much outdated slave

> Subject: Re: [ClusterLabs] Mysql slave did not start replication after failure, and read-only IP also remained active on the much outdated slave On Mon, Aug 22, 2016 at 12:18 PM, Attila Megyeri <amegy...@minerva-soft.com> wrote: > Dear community, > > > > A few days ago we had

Re: [ClusterLabs] Mysql slave did not start replication after failure, and read-only IP also remained active on the much outdated slave

On Mon, Aug 22, 2016 at 12:18 PM, Attila Megyeri wrote: > Dear community, > > > > A few days ago we had an issue in our Mysql M/S replication cluster. > > We have a one R/W Master, and a one RO Slave setup. RO VIP is supposed to be > running on the slave if it is not

[ClusterLabs] Mysql slave did not start replication after failure, and read-only IP also remained active on the much outdated slave

Dear community, A few days ago we had an issue in our Mysql M/S replication cluster. We have a one R/W Master, and a one RO Slave setup. RO VIP is supposed to be running on the slave if it is not too much behind the master, and if any error occurs, RO VIP is moved to the master. Something