I'm pretty happy with this code - we've run it in production with large
cluster (4,200 apache processes, 18 separate cache servers) and tested
server death. Works nicely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
OK - I agree that the best way to do this is to create a new behaviour
type - in fact thinking about this I'd like to make the "retry after
marked dead" time orthogonal to the "retry on timeout" time.
So the behaviour becomes:
1. Server is good - we keep retrying on the timeout until we hit the
** Patch added: "Patch to support server death on consistent distributions with
0.53"
https://bugs.launchpad.net/bugs/881983/+attachment/2573638/+files/0.53-patch1.diff
** Also affects: libmemcached (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification b
note - you'll need to use pylibmc 1.2.1 to reproduce this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881983
Title:
libmemcached resets continuum with dead server
To manage notifications about th
