Re: forcefully taking over a service from another node, kdump

[My LinuxHAList <mylinuxhalist@xxxxxxxxx>]

Thanks Lon for the pointer.

On Mon, Apr 19, 2010 at 11:04 AM, Lon Hohberger <lhh@xxxxxxxxxx> wrote:

On Wed, 2010-04-14 at 14:34 -0400, My LinuxHAList wrote:

>
> === Working on a new solution ===
>
>
> I'm working on a solution for this by a kdump_pre script.
> When node1 panic'ed, before kdumping, it would contact node2 so that
> node2 will attempt to take over the service.
>
>
> At node2, I found <service> running at node1 and issue:
>     clusvcadm -r <service>
>
>
> Because of node1's state (it is kdumping), the command just hangs and
> it did not manage to cut down the service down time.
>
>
> What can I do at node2 to forcefully take over the service from node1
> after node2 is contacted by node1 at kdump_pre stage ?
>

There's a bugzilla open about this -- you should check out

https://bugzilla.redhat.com/show_bug.cgi?id=461948

There's even a design; just no code at this point.

-- Lon

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster