[ClusterLabs] Opt-in cluster shows resources stopped where no nodes should be considered

2016-03-04 Thread Martin Schlegel
Hello all While our cluster seems to be working just fine I have noticed something in the crm_mon output that I don't quite understand and that is throwing off my monitoring a bit as stopped resources could mean something is wrong. I was hoping somebody could help me to understand what it means.

Re: [ClusterLabs] Removing node from pacemaker.

2016-03-04 Thread Andrei Maruha
I have tried it on my cluster, "crm node delete" just removes node from the cib without updating of corosync.conf. After restart of pacemaker service you will get something like this: Online: [ node1 ] OFFLINE: [ node2 ] BTW, you will get the same state after "pacemaker restart", if you

Re: [ClusterLabs] Removing node from pacemaker.

2016-03-04 Thread Dejan Muhamedagic
Hi, On Thu, Mar 03, 2016 at 03:20:56PM +0300, Andrei Maruha wrote: > Hi, > Usually I use the following steps to delete node from the cluster: > 1. #crm corosync del-node > 2. #crm_node -R node --force > 3. #crm corosync reload I'd expect all this to be wrapped in "crm node delete". Isn't that