[Bug 13193] Discussion: strategy for diagnosing memcache issues.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193 --- Comment #12 from David Cook <dcook@prosentient.com.au> --- (In reply to Joonas Kylmälä from comment #4)
I don't think there is corruption happening in memcached but a race condition caused by us using Cache::Memcached::Fast even though it is not thread/fork safe. I fixed this issue by replacing it with Cache::Memcached::Fast::Safe, hopefully I will manage to send a patch soon.
Joonas, you are my favourite person in the world right now. I've been bumping into this problem, and it's been driving me insane. I haven't verified it yet, but I will as soon as I can! -- Reading through the documentation, it looks like we could still use Cache::Memcached::Fast, if we were diligent with the use of "disconnect_all", but that would be a lot of effort to refactor Koha to do that, so I think it would be better to switch to Cache::Memcached::Fast::Safe as you've suggested. The downside is that I don't think Cache::Memcached::Fast::Safe is packaged for Debian (https://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=names&keywords=libcache-memcached-fast-safe-perl), so Mirko would have to package it and put it in Koha's APT repository -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org