[Deploying Sakai] Load balancing and sticky sessions
dave.ross at gmail.com
Tue Apr 13 13:31:49 PDT 2010
Again - why not use cookie based persistence?
On Tue, Apr 13, 2010 at 12:37 PM, Grossman,John E
<john.grossman at mdanderson.org> wrote:
> 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>
>> 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.
>> Jean-Francois Leveque
>> Sakai CTO @ UPMC
>> production mailing list
>> production at collab.sakaiproject.org
>> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org
>> with a subject of "unsubscribe"
> production mailing list
> production at collab.sakaiproject.org
> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
More information about the production