[Pacemaker] Follow up: Colocation constraint to External Managed Resource (cluster-recheck-interval="5m" ignored after 1.1.10 update?)

2013-11-12 Thread Robert H.
Hello, for PaceMaker 1.1.8 (CentOS Version) the thread http://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg18048.html was solved with adding cluster-recheck-interval="5m", causing the LRM to be executed every 5 minutes and detecting externally managed resources as started (in this ca

Re: [Pacemaker] Upgrade of Pacemaker on CentOS 6.4 to 1.1.10 - Delay RA missing ...

2013-11-08 Thread Robert H.
Congratulations! This is the first valid sounding use of Delay I've ever heard :) :) You should file a bug. Opened: https://bugzilla.redhat.com/show_bug.cgi?id=1028421 You're on CentOS, so it may not carry much weight for now, but it does provide a place for other people to "pile on". I'

Re: [Pacemaker] Upgrade of Pacemaker on CentOS 6.4 to 1.1.10 - Delay RA missing ...

2013-11-07 Thread Robert H.
This does a reasonable job of explaining: http://blog.clusterlabs.org/blog/2013/pacemaker-and-rhel-6-dot-4/ I see, thanks for the hint ... small step for man, huge step for mankind .. (or something like this :)) I would be interested to know what for. We have a setup of load balancing v

Re: [Pacemaker] Colocation constraint to External Managed Resource

2013-10-16 Thread Robert H.
Right. Failure timeout is only evaluated on the next pengine run, so if nothing else happens, it takes up to recheck-interval ... Good to know. had to set failure-timeout to the same value (failure-timeout="5m"). You should set it smaller than the recheck interval, I think. Or you may need t

Re: [Pacemaker] Colocation constraint to External Managed Resource

2013-10-15 Thread Robert H.
meta clone-max="2" clone-node-max="1" is-managed="false" property $id="cib-bootstrap-options" \ .. many more options ... cluster-recheck-interval="5m" With this config and some location constraints, the cluster moves virtu

Re: [Pacemaker] Colocation constraint to External Managed Resource

2013-10-14 Thread Robert H.
cemaker to perform a "cleanup" automatically from time to time (I don't want to use cron...) ? Regards, Robert Am 14.10.2013 11:30, schrieb Robert H.: You probably also want to monitor even if pacemaker thinks this is supposed to be stopped. op monitor interval=11s time

Re: [Pacemaker] Colocation constraint to External Managed Resource

2013-10-14 Thread Robert H.
You probably also want to monitor even if pacemaker thinks this is supposed to be stopped. op monitor interval=11s timeout=20s role=Stopped I added this: primitive mysql-percona lsb:mysql \ op start enabled="false" interval="0" \ op stop enabled="false" interval="0" \

Re: [Pacemaker] Colocation constraint to External Managed Resource

2013-10-11 Thread Robert H.
Hello Andreas, Have you verified the mysql script is LSB compliant? http://goo.gl/UqoHbv [root@NODE2 ~]# /etc/init.d/mysql status; echo $? MySQL (Percona XtraDB Cluster) running (10562) [ OK ] 0 [root@NODE2 ~]# /etc/init.d/mysql stop; echo $? Shutting down MySQL (Percona Xtr

Re: [Pacemaker] Colocation constraint to External Managed Resource

2013-10-10 Thread Robert H.
Hello, Am 10.10.2013 16:18, schrieb Andreas Kurz: You configured a monitor operation for this unmanaged resource? Yes, and some parts work as expected, however some behaviour is strange. Config (relevant part only): primitive mysql-percona lsb:mysql \

[Pacemaker] Colocation constraint to External Managed Resource

2013-10-09 Thread Robert H.
Hello list, I have a question regarding colocation. I have an external managed resource (not part of pacemaker, but running on the pacemaker nodes as multi master application) - in this case XtraDB Cluster. I also want to keep this ressource manually managed. For accessing the XtraDb Cluster