Hi,
On a two nodes active/passive cluster, I placed a location constraint of
50 for #uname node1. As soon as applied, things moved from node2 to
node1: right.
I have a lsb init script defined as a resource:
$ crm configure show firewall
primitive firewall lsb:firewall\
op monitor on-fail="restart" interval="10s" \
op start interval="0" timeout="3min" \
op stop interval="0" timeout="1min" \
meta target-role="Started"
This lsb takes a long time to start, at least 55 seconds when fired from
my shell over ssh.
It logs a couple things to std{out,err}.
I have Florian's rsyslog config:
https://github.com/fghaas/pacemaker/blob/syslog/extra/rsyslog/pacemaker.conf.in
So, while node1 was taking-over, I noticed in
/var/log/pacemaker/lrmd.log that it only took 24 seconds to start that
resource.
2012-03-06T07:20:11.844573+01:00 node1 lrmd: [9322]: info:
rsc:firewall:129: start
2012-03-06T07:20:11.864758+01:00 node1 lrmd: [9322]: info: RA output:
(firewall:start:stdout) Starting. Becoming active
[...]
2012-03-06T07:20:35.133591+01:00 node1 lrmd: [9322]: info: RA output:
(firewall:start:stderr) #033[33;01m*#033[0m New rules are now applied.
My question: how comes pacemaker starts a resources twice as fast than I
do from CLI ?
--
Florian Crouzat
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
