[Pacemaker] Node removal in corosync-based cluster

[Dejan Muhamedagic]

Hi,

On Sun, May 29, 2011 at 11:58:17PM +0300, Vladislav Bogdanov wrote:
> Hi all.
> 
> I've got a task to remove some nodes from cluster to save some power and
> found that it is not sufficient to follow
> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-node-delete.html#s-del-ais

Did you try just "crm node delete ..."? That should do whatever's
necessary to remove a node (on which pacemaker be down).

I can vaguely recall this case, but cannot remember anymore what
was the outcome.

Thanks,

Dejan

> After pacemaker is then restarted on any another remaining node, removed
> node comes back in a CIB (with OFFLINE status). Even removal of that
> node from corosync's objdb with
> corosync-objctl -d runtime.totem.pg.mrp.srp.members.COROSYNC_ID
> does not help.
> 
> The only way to completely remove node I found is to stop pacemaker on
> all cluster nodes and start it again then. So there should be some
> 'ghost' data in a running pacemaker instance which is not deleted after
> removal of node data and status from a CIB.
> 
> I hope this could be easily fixed, just a note that it does not fully
> work now (1.1.5 with some patches from both 1.1 and devel).
> 
> Best,
> Vladislav
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker