I don't use this resource in the production. But I think you may to do
experiments with *location *resource.
You also can see my cluster resource Mysql Ping (I use it in the production
for Mysql Master-Master HA) https://github.com/Sov1et/ocf-mysqlping. And
some explain (in кussian). http://habrah
Thanks very much for the link. The percona mysql script does pretty much
exactly what I need in regards to master/slave promotion/demotion. I did
run into a couple of issues revolving around virtual IPs and how they should
follow the master/slave(s) around.
The problem that I'm now running into
Hello.
Check it out https://code.launchpad.net/percona-prm.
And presentation:
http://www.percona.com/files/presentations/percona-live/nyc-2011/PerconaLiveNYC2011-MySQL-High-Availability-with-Pacemaker.pdf
2011/8/15 Michael Szilagyi
> I'm already using the mysql RA file from
> https://github.com/
I'm already using the mysql RA file from
https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/mysql(which
also seems to have replication support in it).
Basically what seems to be happening is that pacemaker detects that the
master has dropped and promotes a slave up to master. Ho
Hi,
On Sat, Aug 13, 2011 at 2:53 AM, Michael Szilagyi wrote:
> I'm new to Pacemaker and trying to understand exactly what it can and can't
> do.
> I currently have a small, mysql master/slave cluster setup that is getting
> monitored within Heartbeat/Pacemaker: What I'd like to be able to do (an
I'm new to Pacemaker and trying to understand exactly what it can and can't
do.
I currently have a small, mysql master/slave cluster setup that is getting
monitored within Heartbeat/Pacemaker: What I'd like to be able to do (and
am hoping Pacemaker will do) is to have 1 node designated as Master
