Re: [ClusterLabs] Restarting parent of ordered clone resources on specific node causes restart of all resources in the ordering constraint on all nodes of the cluster

Hello Strahil, Thank you for your response. The actual problem I wanted to discuss here is restart of ordered resources on unaffected nodes. >From the observation in my original email: 1. I have 4 pacemaker nodes - node2_a node2_b node1_a node1_b 1. I restarted test-1 on node1_a

Re: [ClusterLabs] Restarting parent of ordered clone resources on specific node causes restart of all resources in the ordering constraint on all nodes of the cluster

I was able to fix this by using meta interleave=true on the clones(step 2 below) New steps: 1. Resource creates(same as before): $ sudo pcs resource create test-1 ocf:heartbeat:Dummy op monitor timeout="20" interval="10" clone $ sudo pcs resource create test-2 ocf:heartbeat:Dummy op monitor

[ClusterLabs] Coming in 2.1.3: node health monitoring improvements

Hi all, I'm hoping to have the first release candidate for 2.1.3 ready next week. Pacemaker has long had a feature to monitor node health (CPU usage, SMART drive errors, etc.) and move resources off degraded nodes: https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/singlehtml/index.ht

[ClusterLabs] Antw: [EXT] Coming in 2.1.3: node health monitoring improvements

>>> Ken Gaillot schrieb am 12.04.2022 um 17:22 in Nachricht <33f4147d0f6a3e46581aaa46a4eca81dfa59ce15.ca...@redhat.com>: > Hi all, > > I'm hoping to have the first release candidate for 2.1.3 ready next > week. > > Pacemaker has long had a feature to monitor node health (CPU usage, > SMART drive