mahara-contributors team mailing list archive

[Aaron Wells <785469@xxxxxxxxxxxxxxxxxx>]

Here's a branch on my personal gitorious repo that has this
implementation: https://gitorious.org/mahara/agwells-
mahara/source/79bda3f3d2da7b9b45333bf1d449eff5f94059d5:

That's 1.8_STABLE, with the initial memcache patch and a further commit
that fixes a bug with session.gc_maxlifetime in that initial patch.
We've been using these two patches on several production sites for the
past couple of months without any problems.

As mentioned above, what we need in order to be able to upstream this,
is a $cfg variable to allow the site admin to specify whether to use
standard filesystem sessions, or memcache. Ideally, this would be a
pluggable system to allow for further session types to be implemented,
but at the minimum it'd be fine to just have it hard-coded to memcache
or filesystem.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/785469

Title:
  Support for storing sessions in memcache/redis

Status in Mahara ePortfolio:
  Triaged

Bug description:
  On a busy cluster, storing sessions on an NFS mount creates lot of
  contention on the locks.

  A better solution would be to store sessions in memcache or redis.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/785469/+subscriptions