[Pacemaker] Auto-restart service on IP shift?

[Andrew Beekhof]

On Wed, Feb 3, 2010 at 4:35 PM, Erich Weiler <weiler at soe.ucsc.edu> wrote:
> I think I read about this somehwere, but I can't find it now...  I have a
> cloned service on two nodes that is always running on both (named, one is a
> replicated slave).  The IP sticks to one, then floats to the other if the
> first one goes down.  Works great.
>
> My problem is that named only binds to the IP addrs that are there when it
> comes up, so the second node doesn't bind to the floating IP when it floats
> over there because bind was already started.  If I restart named after the
> IP comes over then it works, but that isn't as automatic as I'd like.  ;)
>
> Is there any way in crm to configure bind to automatically restart on the
> second node if it notices the IP floats over to it?

If you had an ordering constraint that said named clone should start
after the ip, that would achieve what you want.
Might result in extra restarts of the clone though.

What about using a cloned IP too?  Then there'd be no need for rebinding.

>
> Thanks for the continued expert advice...!
>
> -erich
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>