[Koha-bugs] [Bug 13193] Discussion: strategy for diagnosing memcache issues.

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Mon Jan 2 10:44:45 CET 2017


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193

Olli-Antti Kivilahti <olli-antti.kivilahti at jns.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |olli-antti.kivilahti at jns.fi

--- Comment #1 from Olli-Antti Kivilahti <olli-antti.kivilahti at jns.fi> ---
Interesting find.

Do you know if memcached corrupted all the key-values inside it or if this was
an isolated incident which only affected your specific data-structure?

We could add a static checknumber (not calculated from the data) after every
key and val we push to memcached. This shouldn't have much of an overhead and
we could check that the last character in a key or a value must be for ex '!'

This would protect against corruption.
We can log the incident using log4perl and statistize it on a longer duration
to find out if we need to further improve the reliability of memcached?

Offtopic: Cache::Memcached::Fast doesn't have a maintainer any more.

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list