Chuck Mariotti wrote: > Needs to be session aware... other words, users stay on the server they > first hit. If that server goes down, the load balancer detects and fails > over to another web server (session lost). I would love to purchase an > F5 but I think we're at a point where we shouldn't have to shell out > major $ for something this simple.
If you store session info in a shared database instead of on the hdd it alleviates the need for the user to hit the same server. > Round robin won't do... too much downtime and propagation issues that go > with that. As per previous email, setting the TTL to 60 seconds it negates most/all associated DNS problems most people suffer, as for propagation this can be trivially over come as well. If your needs exceed the above requirements it sounds like you need to look into clustering not load balancing. -- Best regards, Duane http://www.cacert.org - Free Security Certificates http://www.nodedb.com - Think globally, network locally http://www.sydneywireless.com - Telecommunications Freedom http://e164.org - Because e164.arpa is a tax on VoIP http://www.freeauth.org - Enterprise Two Factor Authentication "In the long run the pessimist may be proved right, but the optimist has a better time on the trip."
