Are you using evict_outdated_slaves?
<parameter name="evict_outdated_slaves" unique="0" required="0">
<longdesc lang="en">
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 exceeding
the maximum slave lag will merely push down the master preference so
the lagging slave is never promoted to the new master.
</longdesc>
<shortdesc lang="en">Determines whether to shut down badly lagging
slaves</shortdesc>
<content type="boolean" default="${OCF_RESKEY_evict_outdated_slaves_default}" />
</parameter>
On Fri, Nov 11, 2011 at 9:57 PM, Yves Trudeau <y.trud...@videotron.ca>wrote:
> **
> 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 <y.trud...@videotron.ca>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 pacemaker to manage mysql replication. I ran some basic
>> tests on the modified agent and it seems behaving sanely so far but more
>> tests will be needed (next week). I also modified a few things in the RA
>> that were not optimal in my view. Here's the URL for my fork:
>>
>> git://github.com/y-trudeau/resource-agents.git
>> https://y-trud...@github.com/y-trudeau/resource-agents.git
>>
>> In order to use it, you need to adapt the pacemaker configuration, here's
>> the one I am using:
>>
>> http://pastebin.com/QPJPWDhx
>>
>> Next, apart from running more tests, I want to do the following:
>>
>> - review user privileges used, need to lower the ones of replication_user
>> - add support for MHA (http://code.google.com/p/mysql-master-ha/)
>> - run a beautifier for more uniformity in style
>>
>> Reviews and comments are of course welcome.
>>
>> Regards,
>>
>> Yves
>>
>>
>>
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs:
>> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>>
>
>
> _______________________________________________
> Pacemaker mailing list:
> Pacemaker@oss.clusterlabs.orghttp://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
>
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
