[ClusterLabs] Removing node from pacemaker.

[Dejan Muhamedagic]

Hi,

On Fri, Mar 04, 2016 at 01:07:34PM +0300, Andrei Maruha wrote:
> I have tried it on my cluster, "crm node delete" just removes node
> from the cib without updating of corosync.conf.

Ah, I didn't know that this is about udpu where nodes are listed
in 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
> remove a node from corosync.conf and do not call "crm corosync
> reload".

Right, obviously one needs to tell corosync that the
configuration file changed.

Thanks,

Dejan

> 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 corosync del-node <ip_addr>
> >>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 the case?
> >
> >Also, is "corosync reload" really required after node removal?
> >
> >Thanks,
> >
> >Dejan
> >
> >>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, Somanath Jeeva wrote:
> >>>Hi,
> >>>
> >>>I am trying to remove a node from the pacemaker’/corosync cluster,
> >>>using the command “crm_node -R dl360x4061 –force”.
> >>>
> >>>Though this command removes the node from the cluster, it is
> >>>appearing as offline after pacemaker/corosync restart in the nodes
> >>>that are online.
> >>>
> >>>Is there any other command to completely delete the node from the
> >>>pacemaker/corosync cluster.
> >>>
> >>>Pacemaker and Corosync Versions.
> >>>
> >>>PACEMAKER=1.1.10
> >>>
> >>>COROSYNC=1.4.1
> >>>
> >>>Regards
> >>>
> >>>Somanath Thilak J
> >>>
> >>>
> >>>
> >>>_______________________________________________
> >>>Users mailing list: Users at clusterlabs.org
> >>>http://clusterlabs.org/mailman/listinfo/users
> >>>
> >>>Project Home: http://www.clusterlabs.org
> >>>Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> >>>Bugs: http://bugs.clusterlabs.org
> >>_______________________________________________
> >>Users mailing list: Users at clusterlabs.org
> >>http://clusterlabs.org/mailman/listinfo/users
> >>
> >>Project Home: http://www.clusterlabs.org
> >>Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> >>Bugs: http://bugs.clusterlabs.org
> >
> >_______________________________________________
> >Users mailing list: Users at clusterlabs.org
> >http://clusterlabs.org/mailman/listinfo/users
> >
> >Project Home: http://www.clusterlabs.org
> >Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> >Bugs: http://bugs.clusterlabs.org
> 
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org