Add session clustering capability
Description
Activity
Thomas Kelsey April 20, 2021 at 5:11 PM
, since all the subtasks for this issue have been resolved or closed, can this issue be closed?
Daniel McCallum April 9, 2008 at 2:21 PM
As Josh observed in SAK-13330, Sakai-managed ClassLoaders pose interesting problems for distributed session caching. I brainstormed a little bit in that ticket about possible workarounds, all of which reinvent Terracotta's distributed ClassLoader support to some extent. After presenting the problem on the Terracotta forums (http://forums.terracotta.org/forums/posts/list/962.page), it sounds as if Terracotta just might turn out to be the best solution, or at least a solution which involves far less custom plumbing than would any "standard" distributed cache solution. I don't expect it to be entirely painless, but for the time being, we're moving forward with a Terracotta proof-of-concept, which may end up recharacterizing several of the subtasks already created.
And of course, if anyone wants to raise Terracotta red flags, please do. I know there's been concern in the past about the deployment complexity, and I'm not 100% confident on license compatibility...
Details
Priority
MajorAffects versions
Components
Assignee
Daniel McCallumDaniel McCallumReporter
Daniel McCallumDaniel McCallum
Details
Details
Priority
MajorAffects versions
Components
Assignee
Daniel McCallumReporter
Daniel McCallum
This is intended as an umbrella ticket collecting work related to user session clustering as described in more detail here: http://confluence.sakaiproject.org/confluence/x/iwACAQ
At this writing, we're looking at clustering Sakai sessions by replicating session attributes (and possibly other fields) via a distributed cache, probably implemented by ehcache.
Subtickets may be associated with any number of Jira components. I chose to associate this ticket with the "Tool (SVN module)," though, since that's where Sakai's SessionManager is currently factored, and it seemed worthwhile to pick at least one Jira component so as not to drop out of filters someone might construct to look for session-related issues in general. There is a "Clustering (SVN module)" component, that might seem like a better choice, at least w/r/t its name, but as it currently stands that module is mainly concerned with maintaining a registry of Sakai instances associated with a cluster rather than replicating/sharing data (user-scoped or otherwise) within a cluster, which is what we're most interested in at the moment.