** Changed in: libmemcached (Ubuntu)
Status: Confirmed => Fix Released
--
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 no
Some test cases wouldn't pass with the code handling the reset of state,
so I didn't apply that portion of the patch (I still wanted to get in
your other bits).
Want to open a different bug on that so that someone here can track it?
Thanks.
** Changed in: libmemcached
Status: New => Fix R
Great to see the inclusion in 1.0.3.
Having a quick skim of the code in trunk, the changes I made to prevent
server state being reset to new if it was in timeout don't appear to
have been applied. I've not had time to take the build for a spin yet,
has that issue has been dealt with further up th
Just now i found that 1.0.3 has been released out, so i want to know that , is
this bug fixed in 1.0.3?
the behaviour above told is what i need in my cache severs environment.
3ks very much .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
BTW we are getting a couple of test failures after this applied. I am
going to look at it myself and see what the issue might be. We have this
slated for 1.0.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libmemcached (Ubuntu)
Status: New => Confirmed
--
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:
I have a branch which more or less achieves what is described above by
way of a new dead server retry timeout behaviour.
As per the current behaviour with consistent distribution and auto
ejection, keys on the dead server are moved after we hit the initial
failure limit by taking that host out of
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
For this behavior you need to create a new behavior type, and add a test
case.
If we were to apply this patch as is, we would break anyone who is
expecting the current behavior (which comes into play when servers are
replaced in place, or having flapping network service).
** Changed in: libmemcac
The attachment "Patch to support server death on consistent
distributions with 0.53" of this bug report has been identified as being
a patch. The ubuntu-reviewers team has been subscribed to the bug
report so that they can review the patch. In the event that this is in
fact not a patch you can re
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
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
** 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
13 matches
Mail list logo
