[Pacemaker] location anti affinity rule not working

Hi All, I am working on 3 node cluster with corosync+pacemaker on RHEL 6. Eventhough I applied anti-affinity the app is still trying to run on 3rd node. # rpm -qa|grep corosync corosync-1.4.1-17.el6_5.1.x86_64 corosynclib-1.4.1-17.el6_5.1.x86_64 # rpm -qa | grep -i pacemaker

Re: [Pacemaker] lrmd Memory Usage

On 30 Apr 2014, at 9:01 pm, Greg Murphy greg.mur...@gamesparks.com wrote: Hi I’m running a two-node Pacemaker cluster on Ubuntu Saucy (13.10), kernel 3.11.0-17-generic and the Ubuntu Pacemaker package, version 1.1.10+git20130802-1ubuntu1. The problem is that I have no way of knowing

Re: [Pacemaker] location anti affinity rule not working

02.05.2014 03:47, ESWAR RAO wrote: Hi All, I am working on 3 node cluster with corosync+pacemaker on RHEL 6. Eventhough I applied anti-affinity the app is still trying to run on 3rd node. # rpm -qa|grep corosync corosync-1.4.1-17.el6_5.1.x86_64 corosynclib-1.4.1-17.el6_5.1.x86_64 # rpm

Re: [Pacemaker] crmd-transition-delay does not work

This should do it: diff --git a/crmd/cib.c b/crmd/cib.c index 77fa849..50526ca 100644 --- a/crmd/cib.c +++ b/crmd/cib.c @@ -55,6 +55,7 @@ static void do_cib_updated(const char *event, xmlNode * msg) { int rc = -1; +xmlXPathObjectPtr xpathObj = NULL; CRM_CHECK(msg != NULL,

Re: [Pacemaker] location anti affinity rule not working

Hi, It was a copy paste error. But all the configured resources are correct. But still I could see pacemaker trying to start service on common-test-redhat where I kept anti-affinity rule and also the max-clone is 2. Thanks Eswar On Fri, May 2, 2014 at 8:52 AM, Vladislav Bogdanov

Re: [Pacemaker] location anti affinity rule not working

On 2 May 2014, at 2:40 pm, ESWAR RAO eswar7...@gmail.com wrote: Hi, It was a copy paste error. But all the configured resources are correct. But still I could see pacemaker trying to start service on common-test-redhat We cant though. You'll need to send through a crm_report archive

Re: [Pacemaker] Priority Resource Option

On 23 Apr 2014, at 7:01 pm, Robert Dahlem robert.dah...@gmx.net wrote: Hi, the documentation states: If not all resources can be active, the cluster will stop lower priority resources in order to keep higher priority ones active. What I did not find yet: what causes a resource not to be

Re: [Pacemaker] location anti affinity rule not working

Hi, On RHEL6 systems with corosync+pacemaker+crmsh # crm configure property expected-quorum-votes=2 (its not getting changed) # crm configure show node nvsd-common-test-redhat node nvsd-test-redhat-1 node nvsd-test-redhat-2 property cib-bootstrap-options: \