[ClusterLabs] Rework function next_nodeid.

this node again and ... joined node gets id 3. With this fix node id for the first node after rejoin will be set again to 1. Best Regards, Andrei Maruha From 56d99aa764abb2af8d638425b10a1e493d935e4b Mon Sep 17 00:00:00 2001 From: Andrei Maruha <andrei_mar...@epam.com> Date: Wed, 6 Apr 2016

Re: [ClusterLabs] Removing node from pacemaker.

estart", if you remove a node from corosync.conf and do not call "crm corosync reload". On 03/04/2016 12:07 PM, Dejan Muhamedagic wrote: 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 c

Re: [ClusterLabs] Removing node from pacemaker.

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 Instead of steps 1 and 2you can delete certain node from the corosync config manually and run: #corosync-cfgtool -R On 03/03/2016 02:44 PM,

[ClusterLabs] Added optional parameter "name" to "crm corosync add-node"

erLabs/pacemaker/blob/master/lib/cluster/corosync.c). Best Regards, Andrei Maruha /__/ commit 097f26cbbc41fe61e5fff8fece243ed4337ac75d Author: Andrei Maruha <andrei_mar...@epam.com> Date: Wed Jan 27 13:53:22 2016 +0300 added optional parameter [name] to "corosync add-node"