The only reliable way I have found (rhel4 and 5) is this:
1: Migrate all services off the node.
2: Unmount as many GFS disks as possible.
3: Power cycle the node.
The other nodes will recover quickly.
"cman leave (remove) (force)" sometimes works but often doesn't.
--
Linux-cluster maili
On 03/10/2011 02:58 PM, Shi Jin wrote:
> Thank you.
> I think what you did makes perfect sense but on the other hand shouldn't
> the reboot process stop the services in the right order in the first
> place? Maybe there is a timeout issue or they don't necessarily follow
> the right order?
>
> Do y
>
>
>
> What I do is migrate any services from the node to the other member,
> then stop rgmanager->gfs2->clvmd->cman (obviously adapt to what you are
> running). If you have DRBD, then stop it as well. At this point, the
> other node should be the only one in the cluster (confirm with
> 'cman_tool
On 03/10/2011 12:09 PM, Shi Jin wrote:
> Hi there,
>
> I've setup a two-node cluster with cman, clvmd and gfs2. I don't use
> qdisk but had
>
>
> I would like to know what is the proper procedure to reboot a node in
> the two-node cluster (maybe this applies for all size?) when both nodes
> are
Hi there,
I've setup a two-node cluster with cman, clvmd and gfs2. I don't use qdisk
but had
I would like to know what is the proper procedure to reboot a node in the
two-node cluster (maybe this applies for all size?) when both nodes are
functioning fine but I just want to reboot one for some r
