[Quick Fix]
Set memcached to only listen to a single interface.
example memcached setting:
memcached -U 0 -u nobody -p 11222 -t 4 -m 16000 -C -c 1000 -l 192.168.0.1 -v
[Reproducing]
Use attack script (thanks to mala): http://gist.github.com/522741
w/ -l interface restriction: we have
@googlegroups.com
Date: Tue, 24 Aug 2010 23:57:09
To: memcachedmemcached@googlegroups.com
Reply-To: memcached@googlegroups.com
Subject: Re: memcached race condition problem
[Quick Fix]
Set memcached to only listen to a single interface.
example memcached setting:
memcached -U 0 -u nobody -p 11222
Hey,
But if the main thread waits for the conditional variable, who drives
the
main event loop?
Preparing the pipe fd for notifying max conn, and watch it by the
event loop
should be the way.
I should've been more purposefully vague; lets find the easy way to make
it wake up faster. Using
To memcached community,
I have found memcached race condition bug, and here is the detail and
patch that will fix this problem. We would love to hear what this
community think of this patch.
Under normal circumstances, each worker thread accesses its own
event_base
and same goes with main
I forgot to attach path.
here is the URL for patch.
http://kzk9.net/blog/memcached-fix-accept-new-conns-race.patch.txt
This patch was made by Kazuki Ohta(@kaz_mover).
On 8ζ25ζ₯, εεΎ2:42, morimoto shmor...@gmail.com wrote:
I forgot to attach path.
here is the URL for
patch.http://kzk9.net/blog/memcached-fix-accept-new-conns-race.patch.txt
