Load Balancing, Sessions and Temporary Folder
Hi! I would like to know what I should do with the temporary folder in a mutiple Zope with ZEO setup. Does the temporary folder also need a ZEO server? What happens with sessions when the load balancer sends followup requests to different Zopes? Does Plone use Sessions? If not then I might be able to work without them in my case. Any pointers greatly appreciated, Florian Schulze
On Wednesday 18 February 2004 22:00, Florian Schulze wrote:
Hi!
I would like to know what I should do with the temporary folder in a mutiple Zope with ZEO setup. Does the temporary folder also need a ZEO server? What happens with sessions when the load balancer sends followup requests to different Zopes? Does Plone use Sessions? If not then I might be able to work without them in my case.
Any pointers greatly appreciated, Florian Schulze
if you want to keep sessions info between all zeo clients, you need to mount it somewhere there's a recipe a t zopelabs.com by evan, iirc
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Florian Schulze wrote at 2004-2-18 15:00 +0100:
I would like to know what I should do with the temporary folder in a mutiple Zope with ZEO setup. Does the temporary folder also need a ZEO server?
You can use the same ZEO server.
What happens with sessions when the load balancer sends followup requests to different Zopes?
When you store the session info in a storage shared by all clients, all will be well.
Does Plone use Sessions?
Usually not. We use a source IP based load balancing. Thus, usually, successive requests happen to be directed to the same ZEO client. But some customers (usually large companies) have proxy farms. Then requests from the same user may apparently come from different source IPs (corresponding to different proxies). Therefore, we code the ZEO client id in the URL and ensure that our front end webserver passes the request to the correct ZEO client (in the rare case that source IP routing get the wrong web server). -- Dieter
participants (3)
-
Bakhtiar A Hamid -
Dieter Maurer -
Florian Schulze