|
Humm first off, wrong list, please use piranha-list@xxxxxxxxxx before 100's of
zealots/extreme puritians in this list bite you.
Secondly what your asking about is failover methadology specifically 'step down
step up' It is possible to achieve this with the current sw (0.6.0-12) through
a bit of trickery with monitoring scripts. Basically the secondary node would
be given a slightly modified monitoring script to report failure of the current
node if an additional test, added to check availability of the primary node,
spotted that the primary node was available for use again. It's not difficult
to setup and I can give you a hand if you need.
Phil
=--=
Girish Kamath wrote:
> Hi
>
> Sorry, I missed that.
> Iam using piranha on RH High Availability 1.0 Server.
> Iam using nanny/pulse for monitoring. Any idea how do I achieve it with
> nanny/pulse ?
>
> - Girish.
>
> Juri Haberland wrote:
>
> > Girish Kamath <girishkm@xxxxxxxxxxxxxxxx> wrote:
> > > Hi
> > >
> > > I have setup a Linux Virtual Server with 2 load balancers and 2 real
> > > servers. They are working
> > > perfectly fine. When the Primary Load Balancer fails the Secondary Load
> > > Balancer takes control
> > > and starts servicing.
> > > My problem is when the Primary Load Balancer is back in operation again,
> > > it stays as a Secondary
> > > while the original Secondary Load Balancer is servicing requests, as a
> > > primary.
> > > What i want is, that when a Primary LB is back in operation, the
> > > secondary should relinquish the
> > > floating IP to the Primary and Primary should start serving requests
> > > again.
> > > What do i need to do to achive this ? Any pointers would be helpfull
|
