On 2013-03-20 04:11, Quentin Smith wrote:
> On Wed, 20 Mar 2013, Andreas Kurz wrote:
>
>> On 2013-03-19 17:02, Quentin Smith wrote:
>>> Hi-
>>>
>>> I have my cluster configured to use a cloned ping resource, such that I
>>> can write a constraint that I prefer resources to run on a node that has
>
Le 20/03/2013 04:11, Quentin Smith a écrit :
Is there any way to get Pacemaker to delay resource transitions until at
least one full polling cycle has happened, so that in the event of an
outage of the ping target, resources stay put where they are running?
there is the "dampen" parameter
On Wed, 20 Mar 2013, Andreas Kurz wrote:
On 2013-03-19 17:02, Quentin Smith wrote:
Hi-
I have my cluster configured to use a cloned ping resource, such that I
can write a constraint that I prefer resources to run on a node that has
network connectivity. That works fine if a machine loses its n
On 2013-03-19 17:02, Quentin Smith wrote:
> Hi-
>
> I have my cluster configured to use a cloned ping resource, such that I
> can write a constraint that I prefer resources to run on a node that has
> network connectivity. That works fine if a machine loses its network
> connection (the ping attri
Hi-
I have my cluster configured to use a cloned ping resource, such that I
can write a constraint that I prefer resources to run on a node that has
network connectivity. That works fine if a machine loses its network
connection (the ping attribute goes to 0, resources migrate to another
mach
will probably work better if you:
>> * Write the rule correctly ;-)
>
> pingd: defined pingd is a perfectly valid syntax as explained in this
> post
> http://www.woodwose.net/thatremindsme/2011/04/the-pacemaker-ping-resource-agent/
Yes of course it is. I more or less copied t
perfectly valid syntax as explained in this
post
http://www.woodwose.net/thatremindsme/2011/04/the-pacemaker-ping-resource-agent/
I happen to use it just fine.
--
Cheers,
Florian Crouzat
___
Pacemaker mailing list: Pacemaker@oss.clusterlab
On 2012-08-10 16:30, Josh wrote:
> location location_www1-vip www1-vip \
> rule $id="location_www1-vip-rule" pingd: defined pingd
It will probably work better if you:
* Write the rule correctly ;-)
* Formulate it in the "negative" - to banish the service from nodes that
can't reach the g
Hello,
I've followed various docs referring to setting up a ping primitive to monitor
connectivity to, for example, a gateway. If that ping fails, resources that
rely on that ping (or rely on connectivity to the gateway) should failover to
another node. Below is my configuration. I have a ww
right, I added the location-rule and everything works as expected.
Thanks a lot and kind regards
fatcharly
Original-Nachricht
> Datum: Fri, 11 May 2012 15:10:57 +0200
> Von: emmanuel segura
> An: The Pacemaker cluster resource manager
> Betreff: Re: [Pac
hing
moves.
I recommend you read these links:
*
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ch09s03s03.html
*
http://www.woodwose.net/thatremindsme/2011/04/the-pacemaker-ping-resource-agent/
--
Cheers,
Florian Crouzat
___
You are missing di location rule
2012/5/11
> Hi,
>
> I´m using a pacemaker-1.1.6-3.el6.x86_64/corosync-1.4.1-4.el6_2.1.x86_64
> combo on an CentOS 6.2. I´m trying to use a ping-resource to check the
> connectivity to the default gateway. When I deactivate the interface card
> which is connected
Hi,
I´m using a pacemaker-1.1.6-3.el6.x86_64/corosync-1.4.1-4.el6_2.1.x86_64 combo
on an CentOS 6.2. I´m trying to use a ping-resource to check the connectivity
to the default gateway. When I deactivate the interface card which is connected
with default gateway on one node, nothing happens.
th
13 matches
Mail list logo
