Re: [Pacemaker] Adding VIP support for the MySQL RA

On 11-11-12 03:56 PM, Michael Marrotte wrote: An N+1 or N+X topology might be good for that cascading scenario... Find a sweet spot for the evict date. If slave are lagging too much, scale and tune. Hi, That's plainly not always possible since MySQL replication is single threaded. That's

Re: [Pacemaker] Adding VIP support for the MySQL RA

On 11-11-12 02:51 PM, Florian Haas wrote: Hi Yves and Michael, On 2011-11-12 19:22, Yves Trudeau wrote: lol... How many large databases have you managed? Once evicted, MySQL will be restarted by Pacemaker so all the caches will be cold. If I may say so, before you start laughing at people on

Re: [Pacemaker] Adding VIP support for the MySQL RA

An N+1 or N+X topology might be good for that cascading scenario... Find a sweet spot for the evict date. If slave are lagging too much, scale and tune. I haven't read Yves' patch, but I'll check it out. I just saw that he was looking for slave to work with VIP and suggested a couple ways I've

Re: [Pacemaker] Adding VIP support for the MySQL RA

Hi Yves and Michael, On 2011-11-12 19:22, Yves Trudeau wrote: > lol... How many large databases have you managed? Once evicted, MySQL > will be restarted by Pacemaker so all the caches will be cold. If I may say so, before you start laughing at people on the list, it may be a good idea to actual

Re: [Pacemaker] Adding VIP support for the MySQL RA

lol... How many large databases have you managed? Once evicted, MySQL will be restarted by Pacemaker so all the caches will be cold. On a 128GB db server with an InnoDB buffer pool of >100 GB, warming the cache takes hours and during that time the db is much slower. Since the slave has been

Re: [Pacemaker] Adding VIP support for the MySQL RA

Why's evicted terrible? It optional and simply removes the slave node from the cluster if it's lagging too far behind the master. The collocation IP can float to another slave in the cluster or go offline. I thought that's what you're looking for. I can post a config if you're interested. S

Re: [Pacemaker] Adding VIP support for the MySQL RA

Hi, Setting evict_outdated_slaves is terrible but then how do you remove the read VIPs from slaves that are outdated. If there is a way to do it, tell me :) I am always open to do things in a simpler way. This solution works without evicting outdated slaves. The current mysql RA does b

Re: [Pacemaker] Adding VIP support for the MySQL RA

Are you using evict_outdated_slaves? If set to true, any slave which is more than max_slave_lag seconds behind the master has its MySQL instance shut down. If this parameter is set to false in a primitive or clone resource, it is simply ignored. If set to false in a master/slave resource, then e

Re: [Pacemaker] Adding VIP support for the MySQL RA

Because that's not enough, if a slave lags behind too much, I want to remove the vip but not stop the slave. On 11-11-11 06:12 PM, Michael Marrotte wrote: Why don't you simply colocate VIP's with the master/slave roles? On Fri, Nov 11, 2011 at 5:18 PM, Yves Trudeau

Re: [Pacemaker] Adding VIP support for the MySQL RA

Why don't you simply colocate VIP's with the master/slave roles? On Fri, Nov 11, 2011 at 5:18 PM, Yves Trudeau wrote: > Hi, > I created a fork of the resource-agents and modified the mysql RA to > supports VIP. The support for read/write VIPs is something that currently > limits the use of pac

[Pacemaker] Adding VIP support for the MySQL RA

Hi, I created a fork of the resource-agents and modified the mysql RA to supports VIP. The support for read/write VIPs is something that currently limits the use of pacemaker to manage mysql replication. I ran some basic tests on the modified agent and it seems behaving sanely so far but