Srinath brought up the suggestion of efficiently handling sticky sessions in WSO2 LB during a discussion this afternoon. Now we store the mapping of session_id->Member in a Map in the LB. Srinath pointed out that this will be an issue when we have a cluster of LBs & we need to replicate this Map within that cluster. So a better solution would be, to set another cookie which contains the relevant member ID and pass it on to the client. When the client subsequently sends requests, we can retrieve that cookie, find the correct member, and then dispatch the request to that member. This can be implemented with minor changes to the Synapse ServiceDynamicLoadbalanceEndpoint.
In our TenantAwareLoadbalanceEndpoint, we can set the tenant range, and the member ID into the relevant cookies. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
