When using memcached on a site that sells tickets e.t.c. I need to remove the session loss problem in case a particular memcached demon fails. If we can add the ability, perhaps via a setting as it would slow down the default behaviour, to write the users session back to the database when it changes so I can then guarantee a session won't get lost should a memcached server fail. I have something in place to swap out MySQL master servers so that I won't lose data on MySQL.

Opinions?

Comments

catch’s picture

catch
he/him
Primary language English
commented

I think it'd be good to implement this so that session implementations can be chained, or at least examine that first. Then you could do memcache + core database, or memcache + mongodb etc. Would need to be a separate module.

Apparently http://drupal.org/project/cache does chaining of cache implementations, haven't looked at the code though.

jeffsheltren’s picture

jeffsheltren commented
Status: Active » Closed (won't fix)

I agree with OP that this would be a useful feature. And I also agree with catch that it's best to implement this outside of memcache as the 'cache' module has, though I can't speak to that module directly as to how well it works.