Re: [ClusterLabs] Resource-stickiness is not working

2018-06-05 Thread Ken Gaillot
On Wed, 2018-06-06 at 07:47 +0800, Confidential Company wrote: > On Sat, 2018-06-02 at 22:14 +0800, Confidential Company wrote: > > On Fri, 2018-06-01 at 22:58 +0800, Confidential Company wrote: > > > Hi, > > >? > > > I have two-node active/passive setup. My goal is to failover a > > > resource

Re: [ClusterLabs] Resource-stickiness is not working

2018-06-05 Thread Confidential Company
On Sat, 2018-06-02 at 22:14 +0800, Confidential Company wrote: > On Fri, 2018-06-01 at 22:58 +0800, Confidential Company wrote: > > Hi, > >? > > I have two-node active/passive setup. My goal is to failover a > > resource once a Node goes down with minimal downtime as possible. > > Based on my

Re: [ClusterLabs] Resource-stickiness is not working

2018-06-04 Thread Ken Gaillot
On Sat, 2018-06-02 at 22:14 +0800, Confidential Company wrote: > On Fri, 2018-06-01 at 22:58 +0800, Confidential Company wrote: > > Hi, > >  > > I have two-node active/passive setup. My goal is to failover a > > resource once a Node goes down with minimal downtime as possible. > > Based on my

Re: [ClusterLabs] Resource-stickiness is not working

2018-06-01 Thread Ken Gaillot
On Fri, 2018-06-01 at 22:58 +0800, Confidential Company wrote: > Hi, > > I have two-node active/passive setup. My goal is to failover a > resource once a Node goes down with minimal downtime as possible. > Based on my testing, when Node1 goes down it failover to Node2. If > Node1 goes up after

Re: [ClusterLabs] resource-stickiness

2015-09-02 Thread Ken Gaillot
will stay where it is (unless some other > configuration is stronger than the stickiness). If you don't have > resource-stickiness, then once you "unmove", the resource may move to > some other node, as the cluster adjusts its idea of "best". > >> Thanks >>

Re: [ClusterLabs] resource-stickiness

2015-08-28 Thread Rakovec Jost
Subject: Re: [ClusterLabs] resource-stickiness On 08/27/2015 02:42 AM, Rakovec Jost wrote: Hi it doesn't work as I expected, I change name to: location loc-aapche-sles1 aapche role=Started 10: sles1 but after I manual move resource via HAWK to other node it auto add this line: location cli

Re: [ClusterLabs] resource-stickiness

2015-08-27 Thread Ken Gaillot
and...@beekhof.net Sent: Thursday, August 27, 2015 12:20 AM To: Cluster Labs - All topics related to open-source clustering welcomed Subject: Re: [ClusterLabs] resource-stickiness On 26 Aug 2015, at 10:09 pm, Rakovec Jost jost.rako...@snt.si wrote: Sorry one typo: problem is the same

Re: [ClusterLabs] resource-stickiness

2015-08-27 Thread Rakovec Jost
: \ timeout=600 \ record-pending=true BR Jost From: Andrew Beekhof and...@beekhof.net Sent: Thursday, August 27, 2015 12:20 AM To: Cluster Labs - All topics related to open-source clustering welcomed Subject: Re: [ClusterLabs] resource-stickiness

Re: [ClusterLabs] resource-stickiness

2015-08-26 Thread Rakovec Jost
Sorry one typo: problem is the same location cli-prefer-aapche aapche role=Started 10: sles2 to: location cli-prefer-aapche aapche role=Started inf: sles2 It keep change to infinity. my configuration is: node sles1 node sles2 primitive filesystem Filesystem \ params