I'm using cman and have been trying to set the syslog facility for all
of the pacemaker processes (crmd, lrmd, etc) without much luck. So after
google searches failing me on how to configure the syslog facility for
pacemaker when launched from cman, I went digging through the source and
found m
On Thu, Nov 03, 2011 at 01:49:46AM +1100, Andrew Beekhof wrote:
> On Tue, Oct 18, 2011 at 12:19 PM, wrote:
> > Hi,
> >
> > We sometimes fail in a stop of attrd.
> >
> > Step1. start a cluster in 2 nodes
> > Step2. stop the first node.(/etc/init.d/heartbeat stop.)
> > Step3. stop the second node a
Hi Florian,
First of all thanks for getting back to me . You will find my answers inline.
-Original Message-
From: Florian Haas [mailto:flor...@hastexo.com]
Sent: 2011. november 6. 15:34
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Circular replication help needed
Hi.
Yes it is useful in master-master replication for Mysql HA.
How do you see dependency handling in this situation? We want to start
Mysql server on both nodes. So we nee to use clone resorce, right? But in
this case we can't use nether collocation nether group or location tags.
And mysqlping r
The current MySQL RA supports master/slaves which is great. It would be
nice if it supported multiple masters. If I have some free cycles, I'll
look into adding it. I think lots of folks probably use DRBD b/c there's
no RA alternative and they have some experience with it. When standing up
a ne
Attila:
Hope this helps:
primitive p_mysql ocf:heartbeat:mysql \
params binary="/usr/sbin/mysqld" config="/etc/mysql/my.cnf" \
replication_user="xxx" replication_passwd="xxx" \
test_passwd="password" pid="/var/run/mysqld/mysqld.pid" \
socket="/var/run/m
On 2011-11-05 18:20, Attila Megyeri wrote:
> Hello,
>
>
>
> I am having a hard time configuring a relatively simple mysql environment.
>
>
>
> What I’d like to achieve is:
>
> · One master and a slave, with replication
>
> · Relatively quick failover if the master node, or
writes:
>
> Hi All,
> I currently have a 2-node Corosync+Pacemaker cluster configured with a
Shared IP (VIP). When the active node fails, the VIP swings to the passive
node and becomes active - this works very well so far.
>
> Also - on each node is a MySQL instance - a Master/Master rep
