Search Again:

Re: How does loadbalancing work?

From: Aaron Lynch
Date: Friday, May 25, 2001
Time: 12:15:04 am

And of course now you are back to a single point of failure. If the proxy
goes down, your redundant servers are useless.


On 5/24/01 11:51 PM, The Defendant "Men & Mice Support"
<cbuxton@menandmice.com> Confessed:

> For outside browsers, they're hitting the Squid server, which then
> hits the correct (up & running) web server. So outside users aren't
> then affected by this problem of browser memory. It will then only
> affect your internal hosts.
>
> There's a flip side, though - you can't guarantee that an end-user
> will continue to hit the same server throughout their visit. So if
> you have any sort of interactive stuff that needs to track a given
> visitor (WebObjects, Interaction, HTML/OS, etc.), it's going to
> occasionally break as a visitor is diverted to the development
> server, and then back again a few minutes later.
>
> In fact, since it's the Squid server that's getting switched, *all*
> traffic from the outside will hit the main server, except for
> occasional stretches (length determined by your TTL, frequency by
> your load balance settings) where they'll *all* hit the dev server.




Messages In This Thread:



Return to Digital Point Solutions' Home Page