Hey,
32-bit memcached with -m 4000 will never work. the best you can do is
probably -m 1600. 32bit applications typically can only allocate up to 2G
of ram.
memcached isn't protected from a lot of malloc failure scenarios, so what
you're doing will never work.
-m 4000 only limits the slab memory
Nobody pays attention to this?
在 2014年10月29日星期三UTC+8下午4时49分53秒，Samdy Sun写道：
>
> when run out of memory, and use "stats" command, memcached-1.4.20 got
> deadlock.
>
> *STATS_LOCK twice* before unlock.
>
>
> As below calls:
>
> server_stats
> *-->STATS_LOCK();*
> -->APPEND_STAT
> -->append_stat
> -
@Dormando,
I try my best to reproduce this in my environment, but failed. This just
happened on my servers.
I use "stats" command to check the memcached if it is available or not.
If the memcached is unavailable, we will not send request to it.
This is what I feel strange when my cur
Hey,
How are you reproducing this? How many connections do you typically have
open?
It's really bizarre that your curr_conns is "5", but your connections are
disabled? Even if there's still a race, as more connections close they
each have an opportunity to flip the acceptor back on.
Can you prin
