Re: [ClusterLabs] Resource failure-timeout does not reset when resource fails to connect to both nodes

On 03/28/2016 11:44 AM, Sam Gardner wrote: > I have a simple resource defined: > > [root@ha-d1 ~]# pcs resource show dmz1 > Resource: dmz1 (class=ocf provider=internal type=ip-address) > Attributes: address=172.16.10.192 monitor_link=true > Meta Attrs: migration-threshold=3 failure-timeout=30

Re: [ClusterLabs] Using different folder for /var/lib/pacemaker and usage of /dev/shm files

On 05/08/2016 11:19 PM, Nikhil Utane wrote: > Moving these questions to a different thread. > > Hi, > > We have limited storage capacity in our system for different folders. > How can I configure to use a different folder for /var/lib/pacemaker? ./configure --localstatedir=/wherever

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

Hi Klaus, I do it by the weekend of the next week and write a patch using queue. In addition, please tell me your opinion. Many thanks! Hideo Yamauchi. - Original Message - > From: Klaus Wenninger > To: "users@clusterlabs.org" > Cc: > Date: 2016/5/14, Sat 00:51 > Subject: Re: [Clus

Re: [ClusterLabs] start a resource

On 05/06/2016 01:01 PM, Dimitri Maziuk wrote: > On 05/06/2016 12:05 PM, Ian wrote: >> Are you getting any other errors now that you've fixed the >> config? > > It's running now that I did the cluster stop/start, but no: I > wasn't getting any other errors. I did have a symlink resource > "stopped"

Re: [ClusterLabs] Pacemaker with Zookeeper??

On 05/12/2016 02:26 AM, Nguyen Xuan. Hai wrote: > Hi, > > I have an idea: use Pacemaker with Zookeeper (instead of Corosync). Is > it possible? > Is there any examination about that? > > Thanks for your help! > Hai Nguyen It is not currently possible, and there are no plans to support it. I'm n

Re: [ClusterLabs] Antw: Re: Antw: Re: Q: monitor and probe result codes and consequences

On 05/13/2016 06:00 AM, Ulrich Windl wrote: Dejan Muhamedagic schrieb am 13.05.2016 um 12:16 in > Nachricht <20160513101626.GA12493@walrus.homenet>: >> Hi, >> >> On Fri, May 13, 2016 at 09:05:54AM +0200, Ulrich Windl wrote: >> Ken Gaillot schrieb am 12.05.2016 um 16:41 in >> Nachric

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

On 05/13/2016 04:59 PM, renayama19661...@ybb.ne.jp wrote: > i Klaus, > > After all we want transmission order. > I think that I am going to use meta_attribute which you suggested and am > enough. > > (snip) > path="/xxx//xxx.sh"> > > Maybe we find a name that somehow implies what the pu

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

i Klaus, After all we want transmission order. I think that I am going to use meta_attribute which you suggested and am enough. (snip) (snip) I intend to write the correction that included a cue in this meta_attribute, what do you think? I think that processing when queue was changed is

[ClusterLabs] Pacemaker with Zookeeper??

Hi, I have an idea: use Pacemaker with Zookeeper (instead of Corosync). Is it possible? Is there any examination about that? Thanks for your help! Hai Nguyen -- This mail was scanned by BitDefender For more information please visit http://www.bitdefender.com ___

Re: [ClusterLabs] notify action asynchronous ?

Le Thu, 12 May 2016 11:11:15 -0500, Ken Gaillot a écrit : > On 05/12/2016 04:37 AM, Jehan-Guillaume de Rorthais wrote: > > Le Sun, 8 May 2016 16:35:25 +0200, > > Jehan-Guillaume de Rorthais a écrit : > > > >> Le Sat, 7 May 2016 00:27:04 +0200, > >> Jehan-Guillaume de Rorthais a écrit : > >> >

Re: [ClusterLabs] How to add a constraint to move a resource to other node when a resource stop

I found the solution, add colocation constraint like this: pcs constraint colocation add vip-slave with Slave pgsql-master 100 pcs constraint colocation add vip-slave with Master pgsql-master 50 On Fri, May 13, 2016 at 6:08 PM, wd wrote: > hi, > > I'm running a master/slave 2 node PostgreSQL cl

[ClusterLabs] Antw: Re: Antw: Re: Q: monitor and probe result codes and consequences

>>> Dejan Muhamedagic schrieb am 13.05.2016 um 12:16 in Nachricht <20160513101626.GA12493@walrus.homenet>: > Hi, > > On Fri, May 13, 2016 at 09:05:54AM +0200, Ulrich Windl wrote: >> >>> Ken Gaillot schrieb am 12.05.2016 um 16:41 in >> >>> Nachricht >> <57349629.40...@redhat.com>: >> > On 05/12/

[ClusterLabs] :Pacemaker IP Load Balancer and RFC 1812

Hi , We are trying to use the pacemaker load balancer feature. The Load balancer feature uses CLUSTERIP module of the RHEL iptables. CLUSTERIP Load balancer seems to be a RFC 1812 section 3.3.2 violation. For using load balancing option we are going with the MAC generated by the pacemaker IpA

Re: [ClusterLabs] Antw: Re: Q: monitor and probe result codes and consequences

Hi, On Fri, May 13, 2016 at 09:05:54AM +0200, Ulrich Windl wrote: > >>> Ken Gaillot schrieb am 12.05.2016 um 16:41 in > >>> Nachricht > <57349629.40...@redhat.com>: > > On 05/12/2016 02:56 AM, Ulrich Windl wrote: > >> Hi! > >> > >> I have a question regarding an RA written by myself and pacemak

[ClusterLabs] How to add a constraint to move a resource to other node when a resource stop

hi, I'm running a master/slave 2 node PostgreSQL cluster, and 2 virtual ip resource, one is for master, one is for slave. I have add colocation constraint for both virtual ip and master/slave resource, to ensure virtual ip for master is run at master, and virtual ip for slave is run at slave. And

[ClusterLabs] Antw: Re: Q: monitor and probe result codes and consequences

>>> Ken Gaillot schrieb am 12.05.2016 um 16:41 in >>> Nachricht <57349629.40...@redhat.com>: > On 05/12/2016 02:56 AM, Ulrich Windl wrote: >> Hi! >> >> I have a question regarding an RA written by myself and pacemaker > 1.1.12-f47ea56 (SLES11 SP4): >> >> During "probe" all resources' "monitor"