<div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"><div>Hi all,</div><div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; my cluster is corosync-2.0.1(used votequorum) and pacemaker-1.1.7(come from fedora 17).&nbsp; There&nbsp;are three nodes in it (h10_147,h10_148,h10_149). </div><div>&nbsp;&nbsp;&nbsp;&nbsp; I executed the following CLI&nbsp; on&nbsp; h10_147.</div><div><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; <u>/etc/init.d/pacemaker stop</u></em></strong></div><div><strong><em>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<u>/etc/init.d/corosync stop</u></em></strong></div><div>&nbsp;</div><div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;then I&nbsp;executed other CLI on h10_148 to delete the node h10_147</div><div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; <strong><em><u>crm node delete h10_147</u></em></strong></div><div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </div><div>&nbsp;&nbsp;&nbsp;&nbsp; So, I find h10_147 disappeared in cluster by the CLI "<strong><em><u>crm status</u></em></strong>"</div><div>********************************************************************************************&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <div>Stack: corosync</div><div>Current DC: h10_149 (353020096) - partition with quorum</div><div>Version: 1.1.7-1.el6-ee0730e13d124c3d58f00016c3376a1de5323cff</div><div>2 Nodes configured, unknown expected votes</div><div>6 Resources configured.</div><div>============</div><div>Online: [ h10_149 h10_148 ]</div><div>**********************************************************************************************</div><div>&nbsp;</div><div>&nbsp;</div><div>&nbsp;So far, all the state is correct, but the strange problem will happen next.</div><div>&nbsp; I executed the following CLI on h10_148 to try to delete h10_148.</div><div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<strong><em><u> /etc/init.d/pacemaker stop</u></em></strong></div><div><strong><em><u></u></em></strong>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;<strong><em><u>/etc/init.d/corosync stop</u></em></strong></div><div>when I want to delete&nbsp;h10_148 on h10_149 ,&nbsp; I&nbsp;find that the node h10_147 bring back to life in cluster.&nbsp; </div><div>*****************************************************************&nbsp; <div>3&nbsp;Nodes configured, unknown expected votes</div><div>6 Resources configured.</div><div>============</div><div>Online: [ h10_149 ]</div><div>OFFLINE: [ h10_147&nbsp; h10_148 ]</div></div><div>***************************************************************</div><div>&nbsp;what is the reason of this problem ?</div><div>&nbsp;</div><div>Best Regards,</div><div>Mars Gu</div><div>&nbsp;</div></div></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span>