Hi all,
my cluster is corosync-2.0.1(used votequorum) and pacemaker-1.1.7(come
from fedora 17). There are three nodes in it (h10_147,h10_148,h10_149).
I executed the following CLI on h10_147.
/etc/init.d/pacemaker stop
/etc/init.d/corosync stop
then I executed other CLI on h10_148 to delete the node h10_147
crm node delete h10_147
So, I find h10_147 disappeared in cluster by the CLI "crm status"
********************************************************************************************
Stack: corosync
Current DC: h10_149 (353020096) - partition with quorum
Version: 1.1.7-1.el6-ee0730e13d124c3d58f00016c3376a1de5323cff
2 Nodes configured, unknown expected votes
6 Resources configured.
============
Online: [ h10_149 h10_148 ]
**********************************************************************************************
So far, all the state is correct, but the strange problem will happen next.
I executed the following CLI on h10_148 to try to delete h10_148.
/etc/init.d/pacemaker stop
/etc/init.d/corosync stop
when I want to delete h10_148 on h10_149 , I find that the node h10_147 bring
back to life in cluster.
*****************************************************************
3 Nodes configured, unknown expected votes
6 Resources configured.
============
Online: [ h10_149 ]
OFFLINE: [ h10_147 h10_148 ]
***************************************************************
what is the reason of this problem ?
Best Regards,
Mars Gu
_______________________________________________
Pacemaker mailing list: Pacemaker@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://bugs.clusterlabs.org
