Hello Ken, thanks for this information!
> You can make ordering constraints asymmetrical,
> so they only apply in the listed direction:
>
> http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#s-resource-ordering
Ok but i see only how can i create a
On Fri, 2017-10-27 at 13:52 -0500, David Kent wrote:
> Hello,
>
> Is there any way to configure a pacemaker cluster so that a resource
> will restart N times and then stop?
>
> This is essentially a mix of migration-threshold and on-failure=stop.
Not yet. It's a planned future enhancement. It's
On Fri, 2017-10-27 at 14:35 +0200, Stefan Krueger wrote:
> Hello,
>
> is it possible to start a ressource in a different way then they
> stopped?
> eg:
> primitive HA_IP-Serv1 IPaddr2 \
> params ip=172.16.101.70 cidr_netmask=16 \
> op monitor interval=20 timeout=30 on-fail=restart
Hello,
Is there any way to configure a pacemaker cluster so that a resource will
restart N times and then stop?
This is essentially a mix of migration-threshold and on-failure=stop. Let
me describe my setup and what I've tried.
My cluster is a set of independent apps sharing a VIP (all apps are
Thank you for your response! This means that there shoudn't be long "sleep" in
ocf script.
If my service takes 10 minite from service starting to healthcheck normally,
then what shoud I do?
Thank you very much!
> Hi,
> If I remember correctly, any pending actions from a previous transition
>
Hi,
If I remember correctly, any pending actions from a previous transition
must be completed before a new transition can be calculated. Otherwise,
there's the possibility that the pending action could change the state
in a way that makes the second transition's decisions harmful.
Theoretically
I have two clone resources in my corosync/pacemaker cluster. They are fm_mgt
and logserver. Both of their RA is ocf. fm_mgt takes 1 minute to start the
service(calling ocf start function for 1 minite). Configured as below：
# crm configure show
node 168002177: 192.168.2.177
node 168002178:
I have two clone resources in my corosync/pacemaker cluster. They are fm_mgt
and logserver. Both of their RA is ocf. fm_mgt takes 1 minute to start the
service(calling ocf start function for 1 minite). Configured as below：
# crm configure show
node 168002177: 192.168.2.177
node 168002178:
On Fri, 2017-10-27 at 16:28 +0600, Sergey Korobitsin wrote:
> Hello,
> I'm trying to use https://github.com/marcan/pacemaker-exporter,
> and it wants 'expected' node attribute from my crm_mon -X output,
> but it's missing. Is that because I'm using no-quorum-policy=ignore?
Quorum policy won't
On Thu, 2017-10-26 at 19:09 +1100, Huw Davies wrote:
> I was wondering if anyone had looked into getting cluster metrics
> (counters and performance) and exposing them via collect?
>
> We’re about to go live with a large application on a four node RHEL
> and are interested in understanding the
Does anyone know this question?
best regards
发自网易邮箱手机版
在2017年10月25日 23:10，lkxjtu 写道：
My problem is about the pacemaker. For example,the pacemaker cluster has two
resources, both of them resource agent are ocf. One of resource is
starting(calling ocf start function), such as needing for 1
Hello,
is it possible to start a ressource in a different way then they stopped?
eg:
primitive HA_IP-Serv1 IPaddr2 \
params ip=172.16.101.70 cidr_netmask=16 \
op monitor interval=20 timeout=30 on-fail=restart nic=bond0 \
meta target-role=Started
primitive HA_IP-Serv2
Hello,
I'm trying to use https://github.com/marcan/pacemaker-exporter,
and it wants 'expected' node attribute from my crm_mon -X output,
but it's missing. Is that because I'm using no-quorum-policy=ignore?
--
Bright regards, Sergey Korobitsin,
Chief Research Officer
Arta Software,
13 matches
Mail list logo
