Comments on: Started memcached session manager project: session failover with memcached

by: martin.grotzke

Mon, 11 Apr 2011 21:54:20 +0000

D’oh, just found the filled up comment queue - sorry for being quite that long!

@Hank: Sounds good, that’s basically what I just implemented in msm 1.4.0 to support non sticky sessions. I also invite to discuss things in greater detail on the mailing list (http://groups.google.com/group/memcached-session-manager ).

by: ehcache.net

Tue, 04 Jan 2011 04:02:51 +0000

Started memcached session manager project: session failover with memcached…

I just started my first project on google code with the source code hosted in github: the memcached session manager.

– At first I must say - creating new projects on google code or github feels completely different compared to some years ago when pr…

by: Hank

Thu, 19 Mar 2009 17:04:04 +0000

Here is my opinion. It is better to remove the session sticky requirement and move the session out of tomcat completely. The session can be store in two tiers memecached servers: frontend and backup.

here is the read flow, user -> any tomcat -> read session out from frontend memcached with session id.
Here is the store flow, session changed -> store to frontend memcached server with session id as key -> store to backup memcached server with session id as key.

Here is the failover case.
if one tomcat is down, user will connect to another tomcat server without issue.
if one memcached server is down, read the data from backup memcached server.

So if the tomcat session handling code can be changed to connect to memcached directly, there is no need to change the application or add servlet to application.

your opinion?