There's a lot of variables involved with that question. Depends on how the server is going down (loss of power, health check, etc). Because there are so many different reasons it could take a large amount of time to come back online, any suggestions are bad guesses.
Things to keep in mind: - you may have no-fast-bringup globally or on a specific port - your health check may be waiting on something else to bring up the port - you may have sticky persistence etc. Scott On Tue, Apr 19, 2011 at 8:01 AM, Drew Weaver <[email protected]> wrote: > Hi Scott, > > > > Thank you for that tip that got me where I needed to be. > > > > My last question is it seems to take rather a long time (3-4 minutes) for > it to switch back to the main servers after they come back up. > > > > Is there some way to make that faster? > > > > thanks, > > -Drew > > > > > > *From:* Scott T. Cameron [mailto:[email protected]] > *Sent:* Monday, April 18, 2011 8:38 PM > *To:* Drew Weaver > *Cc:* [email protected] > *Subject:* Re: [f-nsp] ServerIron: direct requests to alternate server if > all real servers are down. > > > > backup is correct. > > > > You need to add 'port # lb-pri-servers' on the vserver. > > > > Scott > > On Mon, Apr 18, 2011 at 8:19 PM, Drew Weaver <[email protected]> > wrote: > > Hi, > > How can you make a serveriron XL send requests to a different server only > if the primary server(s) fail healthchecks? > > I tried setting the secondary server as a backup server but the load > balancer was balancing traffic between the primary servers and the 'Backup > server' I only want requests to be sent to the backup server in the event > the other real servers are offline. > > Thanks, > -Drew > > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp > > >
_______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
