Hi,
I think the drbd RA can not have two masters! So master-max should be one.
Thanks
hj
On Fri, Jul 17, 2009 at 12:49 PM, Michael Schwartzkopff
wrote:
> Hi,
>
> I configured a multistate DRBD (dual master) and OCFS2 on my cluster. I
> want to
> mount the filesystem where DRBD is master. The fo
Ever since I plugged ocfs in to pacemaker, I've been having issues with my
cluster's stability. Thankfully, we're still testing things and not in
production yet, but ...
Specifically, this error has started to show up:
Jul 17 12:37:02 app-03 openais[5009]: [crm ] ERROR: route_ais_message: Ch
Hi,
I configured a multistate DRBD (dual master) and OCFS2 on my cluster. I want to
mount the filesystem where DRBD is master. The following config seems to do the
trick:
primitive resDRBD ocf:linbit:drbd \
operations $id="resDRBD-operations" \
op monitor interval="20" role="Sla
Hi Nikola,
On Fri, 2009-07-17 at 07:21 +0200, Nikola Ciprich wrote:
> Hello,
> few days ago, I asked about python bindings, since then, I played a
bit with
> pacemaker-mgmt package, especially the pymgmt class. I was able to
create very simple
> python management class using it, which could be use
2009/7/17 :
> Hi Andrew,
>
>> What do you mean by monitor here?
>> Do you mean that pacemaker would no longer detect if those two processes
>> died?
>
> This monitor means the monitor of the resource.
> When these processes fall, the monitor of the resource of lrmd/stonithd stops.
> For example,
Hi,
primitive resDRBD ocf:linbit:drbd \
operations $id="resDRBD-operations" \
op monitor interval="20" role="Slave" timeout="20" start-delay="1m" \
op monitor interval="10" role="Master" timeout="20" start-delay="1m" \
params drbd_resource="r0" \
meta $id="r
Hi Andrew,
> What do you mean by monitor here?
> Do you mean that pacemaker would no longer detect if those two processes died?
This monitor means the monitor of the resource.
When these processes fall, the monitor of the resource of lrmd/stonithd stops.
For example, the monitor of external/ssh a
On Fri, Jul 17, 2009 at 3:34 AM, wrote:
> Hi,
>
> We began shift investigation to the combination of Pacemaker and
> corosync/openais now.
>
> We put Pacemaker and openais(whitetank) together and confirmed movement at
> the time of the process
> trouble.
> (This is the function that a reboot eme
