[Deploying Sakai] Load balancing and sticky sessions

[Grossman,John E]

I'm not sure - we haven't tested non-SSL. We use SSL for everything - even
resources. I'm going to look into cookie-based persistence when we change
over to a new load balancer in the near future.


On 4/14/10 3:16 AM, "Jean-Francois Leveque" <jean-francois.leveque at upmc.fr>
wrote:

> Do you think this might happen without SSL, John?
> 
> Grossman,John E a écrit :
>> Slightly unrelated - We have had some issues using Cisco CSS and SSL sticky
>> sessions. The CSS load balancer occasionally seems to lose track of the SSL
>> session and directs requests from an existing Sakai session to the wrong
>> server, causing the user to have to re-authenticate. Not sure if it is a CSS
>> configuration issue, a CSS bug or something else.
>> 
>> 
>> On 4/13/10 7:16 AM, "Jean-Francois Leveque" <jean-francois.leveque at upmc.fr>
>> wrote:
>> 
>>> Hi all,
>>> 
>>> The current UPMC load balancing is done by IP-based sticky sessions.
>>> 
>>> This is inefficient with users going through proxies and requests done
>>> by the main portal on behalf of users.
>>> 
>>> Our load-balancer admin offered to do the load-balancing based on a
>>> parameter in the URL sur as:
>>> 
>>> http://<sakai instance domain name>/...?server=<serverId>
>>> 
>>> Can this be done and if it can, how do I do this ?
>>> 
>>> Please note that each Tomcat server is behind its own apache HTTPD
>>> server  and accessed through mod_proxy.
>>> 
>>> Cheers,
>>> 
>>> --
>>> Jean-Francois Leveque
>>> Sakai CTO @ UPMC