On Thu, Jan 22, 2009 at 6:18 AM, Voltron <[email protected]> wrote: > Great! > > On Jan 22, 1:26 pm, Alvaro Lopez Ortega <[email protected]> wrote: >> On 22-ene-09, at 10:57, Stefan de Konink wrote: >> >> > Voltron wrote: >> >> Thanks guys. I have an existing application that uses sessions that I >> >> would like to migrate, I would need session support. Could you point >> >> me to the relevant docs? Is the hash IP method a separte application >> >> or an option in Chereokee? I could not find any documentation on it. >> >> > Select instead of Round Robin, Hasp IP in the webinterface. Most >> > likely >> > you want the SVN version of Cherokee. >> >> The IP Hash load balancer is part of the upcoming Cherokee 0.98 >> release. My plan is to release it within the next days (as soon as we >> get to fix a couple of lingering bugs).
Another option thats cleaner IMHO is a shared nothing architecture where your application nodes don't store any cross-request state. Ideally session state is stored clientside and persistent data is stored in a data store (eg filesystem, rdbms, couchdb, etc.) shared by all application nodes. Now I realize there's one big problem with that ideal situation: by default PHP stores sessions as files. IMHO this is a design flaw for which load balancing by IP Hash is a nice hack, but I'm sure there are plenty of smarter people than I running successful web sites using this technique. :-) So if you get to design your entire web application stack from the ground up, go shared-nothing and then load balancing is trivial. If you're already storing data on the application node, IP Hash is a fine solution. Just my $0.02 I'm no load balancing pro, so I could be way off. ;-) _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
