Comment #4 on issue 101 by [email protected]: Not reading server
responses will hang the server
http://code.google.com/p/memcached/issues/detail?id=101
I just built memcached-1.4.20 on RHEL6 against libevent-1.4.13, that come
from RedHat and had no problems.
I then read, that using libevent-2.x improves performance substantially,
and tried using that. Memcached builds fine:
% ldd ...../BUILD/memcached-1.4.20/memcached-debug
linux-vdso.so.1 => (0x00007fffe17ff000)
libevent-2.0.so.5 =>
/local/packages/libevent/lib64/libevent-2.0.so.5 (0x00007fab2c0af000)
librt.so.1 => /lib64/librt.so.1 (0x00007fab2bea6000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fab2bc89000)
libc.so.6 => /lib64/libc.so.6 (0x00007fab2b8f6000)
/lib64/ld-linux-x86-64.so.2 (0x00007fab2c308000)
but the self-test fails:
...
ok 8 - strtol
ok 9 - strtoll
ok 10 - strtoul
ok 11 - strtoull
ok 12 - issue_44
ok 13 - vperror
< HANG >
The stderr fills up with messages repeated as much as the xterm can handle:
[warn] libevent2 event_del: event has no event_base set
I disabled the warning-message with the attached patch, but the test 14
(issue_101) still hangs.
Again, when using libevent-1.4.x everything is fine... Please, advise -- I
would like to use libevent-2.x if possible. Thank you!
Attachments:
patch-event_del 298 bytes
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
