Hi,
On Thu, May 21, 2009 at 03:30:53PM -0700, Joe Armstrong wrote:
> I have a small testing cluster that has no stonith devices, I
> want to see how reactions occur when node kills are needed and
> I was wondering if there was a way to tell stonithd that the
> kill has completed (I don't think nul
Hi Junko-san,
On Thu, May 21, 2009 at 06:32:52PM +0900, Junko IKEDA wrote:
> Hi,
>
> I have 4 nodes (dl380g5a, dl380g5b, dl380g5c, dl380g5d),
> and run 1 clone resource with the following configuration.
> clone_max"="2"
> clone_node_max"="1"
>
> (1) Initial state
> dummy:0 dl3
Well, I'm still not sure what the state of OpenAIS/CoroSync is, but seem to encounter only more problems the farther I
dig in to it. Here are the versions of the software packages I'm using:
corosync0.92-0ubuntu3
libcorosync-dev 0.92-0ubuntu3
libcorosync20.92-0ubuntu3
li
I have a small testing cluster that has no stonith devices, I want to see how
reactions occur when node kills are needed and I was wondering if there was a
way to tell stonithd that the kill has completed (I don't think null stonith
will do what I need). In other words, I am getting the messages
Hi,
On Wed, May 20, 2009 at 03:09:30PM -0400, Ryan Steele wrote:
> Hey folks,
>
> Been toying with OpenAIS and Pacemaker for a day or two, and I have a few
> questions that I couldn't find verbiage on in the documentation, which I
> hope some wiser minds might be able to answer.
>
> 1. Is there
I have tried several things with resource constraints and roles (Master, Slave,
and Started), but cannot seem to get both of these conditions to be met:
- When the master pingd fails, set a negative score to force failing
over to the other node
- When the failover is complete
As someone who is just getting acquainted with a world that is no longer
just DRBD + Heartbeat, I find myself a bit confused on exactly what I
should be using - CoroSync or OpenAIS?
I was using OpenAIS + Pacemaker in my first few days of testing, but I
then upgraded only to find that the aise
Hi:
The wiki says that DRBD primary/primary isn't supported yet:
http://clusterlabs.org/wiki/DRBD_HowTo_1.0
Is there a workaround?
Regards,
Nick
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/
Is there a way to time-out the failure of PingD?
In my configuration, I cannot run PingD all the time on every node. Only one
node (the master) has public Internet access. I use PingD to cause the master
to fail-over to one of the slaves. When a slave becomes master, it then gains
public Intern
To send in unique information, you will need to create individual instances of
each. Then you will need to use location constraints to lock them down to
individual nodes.
Alternatively, you could re-write the RA so that you can pass it a
host-to-parameter mapping string like:
name="mydata" val
> -Original Message-
> From: Infos E-Blokos [mailto:in...@e-blokos.com]
> Sent: Thursday, May 21, 2009 9:16 AM
> To: pacema...@clusterlabs.org
> Subject: Re: [Pacemaker] globally-unique clone question
>
>
> - Original Message -
> From: "Eliot Gable"
> To: "pacemaker@oss.cluster
- Original Message -
From: "Eliot Gable"
To: "pacemaker@oss.clusterlabs.org" ;
"JoeArmstrong"
Sent: Thursday, May 21, 2009 11:39 AM
Subject: Re: [Pacemaker] globally-unique clone question
The typical usage in this case would be to make all mail servers serve all
domains (virtual d
The typical usage in this case would be to make all mail servers serve all
domains (virtual domain support) and then run N instances across those N
servers. Then there is no per-server unique information to deal with. Then you
can run, for example, load sharing between the nodes using iptables C
Hi All,
I am a little confused about globally-unique clones, since there can be no
instance attributes for a clone how do you tell each clone that it is unique ?
My use case is that we need to run N instances of a mail server, each mail
server is unique in that it serves a specific domain, two
Sorry,
There were some wrong explanations.
> (4) Now, the failconts for dummy:1 are;
> dl380g5c = 1
> dl380g5d = 1
(4) Now, the failconts for dummy:1 are;
dl380g5b = 1
dl380g5c = 1
> After set value "0",
> The failcount was deleted not only for dl380g5c but also dl38
15 matches
Mail list logo
