[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

David Cook <dcook at prosentient.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au

--- Comment #3 from David Cook <dcook at prosentient.com.au> ---
(In reply to Christian McDonald from comment #2)
> That makes sense, though that's conflicting with what I'm reading about
> scaling out memcached in this way. So then, what is the point of having
> multiple memcached servers (which can be configured in koha-conf.xml)? As I
> understand memcached (which I will admit is novice at best), the use of
> multiple servers is completely up to the memcached client
> implementation...something along the lines of hashing each keyitem against
> the server list, effectively tying a keyitem to a single node in the
> cluster. Because the number of nodes is known by all clients, this should
> effectively distribute keys across the nodes and ensure a cached value only
> lives on one node at a time. If a node goes down, those keys are simply
> rebased on another node.
> 
> I might be completely off here too lol

I haven't set up a memcached cluster but I think it should be fine so long as
it's configured correctly

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