** Package changed: libmemcached (Ubuntu) => libmemcached
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931696
Title:
Server timeout state reset on IO error
To manage notifications about this bug g
Public bug reported:
When an IO error is encountered the server state is reset to
MEMCACHED_SERVER_STATE_NEW even if it is currently
MEMCACHED_SERVER_STATE_IN_TIMEOUT. The call to
memcached_mark_server_for_timeout will then incorrectly push the next
connection retry time further back and further
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
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
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/32178173/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/32178174/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/32178175/BootDmesg.txt
** Att
Public bug reported:
Suspend seems to complete succesfully, and power light starts blinking.
Pressing power button to begin resume results in disk activity so the
process evidently starts, unfortunately the screen remains blank and
there is no apparent response to input.
Running karmic (although
