Updates:
Status: Fixed
Comment #12 on issue 106 by dorma...@rydia.net: binary protocol parsing can
cause memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
think this was merged up. closing.
Comment #11 on issue 106 by pi3or...@gmail.com: binary protocol parsing can
cause memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
I think you are right.
In my first patch (Comment 1), the recvfrom() call is critical because in
that situation, if a UDP socket
Comment #10 on issue 106 by dorma...@rydia.net: binary protocol parsing can
cause memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
The incoming packet is consumed in try_read_udp(), so if you get into a
conn_close state after reading one packet, calling an emp
Comment #9 on issue 106 by pi3or...@gmail.com: binary protocol parsing can
cause memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
The recvfom() use 0 as SIZE and NULL as BUFFER. According to manual, that
call will consume the incoming packet. Without it, epoll
Updates:
Status: Started
Owner: trond.no...@gmail.com
Comment #8 on issue 106 by dorma...@rydia.net: binary protocol parsing can
cause memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
I just pulled a patch similar to this into my 1.4.7 tree.
Thi
Comment #7 on issue 106 by pi3or...@gmail.com: binary protocol parsing can
cause memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
Ok. 1.6.0-beta1 still suffer from this problem, the principle is similar.
Following patch solve it (I thought).
--- ./daemon/me
Comment #6 on issue 106 by dorma...@rydia.net: binary protocol parsing can
cause memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
Can you issue a patch against 1.6.0-beta1? Or were you talking about 1.4.5,
not 1.3.5?
Comment #5 on issue 106 by pi3or...@gmail.com: binary protocol parsing can
cause memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
Hello again! I (the author of http://gitorious.org/snitchaser) has
disappeared for nearly 10 month, and now come back to continue
Comment #4 on issue 106 by airat.ha...@gmail.com: binary protocol parsing
can cause memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
may be this specific issue is solved by the provided patch (haven't tried),
but in general the problem remains.
Even after applyi
Updates:
Owner: eric.d.lambert
Comment #3 on issue 106 by eric.d.lambert: binary protocol parsing can
cause memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
this looks similar to the problem with issue 158, so i'll take a look at
this
Comment #2 on issue 106 by pi3orama: binary protocol parsing can cause
memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
The issue is studied and solved under the help of Snitchaser:
http://gitorious.org/snitchaser
Comment #1 on issue 106 by pi3orama: binary protocol parsing can cause
memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
The root cause of this issue is try_read_udp() never reset c->rbytes.
The processing of conn_nread minus c->rbytes by c->rlbytes, so if extra
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 106 by mar...@hyves.nl: binary protocol parsing can cause
memcached server lockup
http://code.google.com/p/memcached/issues/detail?id=106
What steps will reproduce the problem?
1. run a memcached server on localhost port 1
13 matches
Mail list logo
