[Koha-bugs] [Bug 25158] New: Introduce koha-memcached
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Wed Apr 15 14:28:44 CEST 2020
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25158
Bug ID: 25158
Summary: Introduce koha-memcached
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: Packaging
Assignee: koha-bugs at lists.koha-community.org
Reporter: magnus at libriotech.no
QA Contact: testopia at bugs.koha-community.org
CC: mirko at abunchofthings.net
"Interacting" with memcached has been a problem, since pretty much the only
thing we can easily do with it is restart it to empty it of all cached values.
This is less than ideal, especially in a multi-tenant setup where several Koha
instances share the same server, and also the same memcached server. This is
especially true when sessions are saved in memcached, which means that
"flushing" (restarting) the cache for one site terminates all active sessions
for all sites.
koha-memcached tries to fix this by providing a convenient script to list all
keys in memcached, get their values and delete them. This is done as a script
similar to koha-mysql etc.
Now, while researching this I read that doing things like listing all keys in
memcached might not always be possible. It does seem to work in the testing I
have done so far though. Maybe a single instance of memcached on localhost is
less problematic in this respect then if you have a cluster of servers etc?
More opinions on this is needed.
The script relies on Memcached::libmemcached and memcdump.
This is mostly a proof of concept, with some rough edges that need to be worked
on a bit more, *if* this approach is something we think is worth pursuing.
Feedback is most welcome!
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
More information about the Koha-bugs
mailing list