[Koha-bugs] [Bug 27078] Starman hanging in 3-node Koha cluster when 1 node goes offline.

[bugzilla-daemon at bugs.koha-community.org]

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

--- Comment #12 from Christian McDonald <rcmcdonald91 at gmail.com> ---
I think Memcached is likely the culprit. However, if I recall correctly, I
actually reconfigured koha-conf.xml in my testing to ONLY point to
localhost:11211 memcached. So each Koha node was only looking at the memcached
instance on itself and not distributing keys among the other two nodes. In this
case, the results were the same. Weird. I'm still mulling over everything in
your latest post, but I think I need learn how to do some perl profiling and
see what methods are hanging up this process.

On another note, has there been any discussion concerning other in-memory
caching solutions, like redis? How much work would be involved in supporting
another caching solution? It appears that most (if not all) of the caching
abstraction is wrapped up in Koha::Cache. I'm not a perl expert but it seems
based on the code that Koha defaults to fastmap if memcached isn't configured?

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