I've recently started taking a look at pacemaker to get some kind of HA in a
mysql test environment. The grouping has a ocf:heartbeat:IPaddr2 and a
ocf:heartbeat:mysql monitor in it. The IP monitor spins up fine and
properly jumps around the cluster depending on which node is active. I'm
having
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
missing.
-Mike.
On Mon, Aug 15, 2011 at 1:56 AM, Dan Frincu wrote:
> 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 curren
be727-1552-4028-ad8a-cf54b2766da0): online
p_sql:0 (ocf::percona:MySQL_replication) Slave
writer_vip (ocf::heartbeat:IPaddr2) Started
Node seven (bb15cdbc-8bec-4f64-83bb-8bbd6d4ca1a7): online
p_sql:2 (ocf::percona:MySQL_replication) Slave
As always, any ideas/suggestion
I'm having a problem with master/slave promotion using the most recent
version of the mysql ocf script hosted off the clusterLabs/resource-agents
github repo.
The script works well failing over to a slave if a master looses connection
with the cluster. However, when the master rejoins the cluster
nyone?
On Fri, Aug 26, 2011 at 10:19 AM, Michael Szilagyi wrote:
> I'm having a problem with master/slave promotion using the most recent
> version of the mysql ocf script hosted off the clusterLabs/resource-agents
> github repo.
>
> The script works well failing over to a
