[Pacemaker] stop problem and crm node delete nodename is bug?

[jiaju liu]

Date: Tue, 28 Sep 2010 12:27:47 +0200
From: Andrew Beekhof <andrew at beekhof.net>
To: The Pacemaker cluster resource manager
    <pacemaker at oss.clusterlabs.org>
Subject: Re: [Pacemaker] pacemaker stop problem
Message-ID:
    <AANLkTikoqp6bpEcxChxRVqSAshhBW=1KsV7SHjXBSMBG at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

On Tue, Sep 28, 2010 at 10:00 AM, jiaju liu <liujiaju86 at yahoo.com.cn> wrote:

> hi guys
> I use  command service openais force-stop to stop openais, It ofen waste a
> long time to stop or maybe run this command and no end. sometimes I
> use command service openais force-stop twice it will be ok, or I have to
> kill pocess. who has a better way to stop service.
>
>
More than likely openais is waiting for pacemaker, and pacemaker is waiting
for one of your cluster services to stop.
Figure out why thats taking so long and you'll solve the issue.
 
Are there any command to turn off pacemaker???
and I find some problem about crm node delete nodename. 
If your delete node is DC the cluster will not vote new DC, so DC is NONE. Besides these ,although the cluster could not see this node ,the node could use crm_mon to see cluster. and If filesystem resource is running on this node, after execute command crm node delete nodename, the filesystem will not umount, so this resource could not migrate to other node in cluster I think this is a bug.



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100929/3a054d52/attachment-0001.html>