Re: [ClusterLabs] attrd does not clean per-node cache after node removal

On 03/23/2016 12:01 PM, Vladislav Bogdanov wrote: > 23.03.2016 19:52, Vladislav Bogdanov wrote: >> 23.03.2016 19:39, Ken Gaillot wrote: >>> On 03/23/2016 07:35 AM, Vladislav Bogdanov wrote: Hi! It seems like atomic attrd in post-1.1.14 (eb89393) does not fully clean node cache

Re: [ClusterLabs] Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

Le Thu, 19 May 2016 13:15:20 -0500, Ken Gaillot a écrit : > On 05/19/2016 11:43 AM, Jehan-Guillaume de Rorthais wrote: >> Le Thu, 19 May 2016 10:53:31 -0500, >> Ken Gaillot a écrit : >> >>> A recent thread discussed a proposed new feature, a new

Re: [ClusterLabs] Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

Le Thu, 19 May 2016 10:53:31 -0500, Ken Gaillot a écrit : > A recent thread discussed a proposed new feature, a new environment > variable that would be passed to resource agents, indicating whether a > stop action was part of a recovery. > > Since that thread was long and

[ClusterLabs] Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

A recent thread discussed a proposed new feature, a new environment variable that would be passed to resource agents, indicating whether a stop action was part of a recovery. Since that thread was long and covered a lot of topics, I'm starting a new one to focus on the core issue remaining: The

Re: [ClusterLabs] Node attributes

On 05/18/2016 10:49 PM, ‪H Yavari‬ ‪ wrote: > Hi, > > How can I define a constraint for two resource based on one nodes > attribute? > > For example resource X and Y are co-located based on node attribute Z. > > > > Regards, > H.Yavari Hi, See

[ClusterLabs] Antw: Pacemaker restart resources when node joins cluster after failback

>>> Dharmesh schrieb am 19.05.2016 um 13:18 in >>> Nachricht : > Hi, > > i am having a 2 node Debian cluster with resources configured in it. > Everything is working fine apart from one thing. Usually

[ClusterLabs] Pacemaker restart resources when node joins cluster after failback

Hi, i am having a 2 node Debian cluster with resources configured in it. Everything is working fine apart from one thing. As and when one of my two node joins the cluster, the resources configured on currently active node gets restarted. I am not able to figure out why cluster is behaving like