also seeing this exact behavior on debian wheezy using the dotdeb.org
packages...
On Wednesday, 15 October 2014 17:57:37 UTC+2, Flick Flack wrote:
Hi all,
Migrated to a new server and I'm now encountering unexpected Memcache
session behaviors.
First my config :
- Windows Server 2008 R2
Hey,
I also got a stuck when specifing -m 200.
As mentioned previously, that case could happend as below?
* 1. malloc fails when conn_new()*
* 2. event_add fails when conn_new()*
* 3. other case?*
And I find another case after code reviewing. Here is, memcached stuck
for a while,
There're too many things that will go wrong if malloc fails...
There's a stats counter covering some of them. Is that going up for you?
Have you disabled overcommit memory? Have you observed the process size
when it hangs? malloc should almost never actually fail under normal
conditions...
On
@Dormando,
I think it's not because of malloc fails.
I use -m 200 and there is 48G ram of my server.
After close(c-sfd), I printf a message as fprintf(stderr,
INFO`fd=%d`reason=%s`allow_new_conns=true\n, c-sfd, conn_close);
Here are the codes,
* static void conn_close(conn *c) {*
*
Additionally, the stats counter of malloc_fails is ok.
(gdb) p stats
$1 = {mutex = {__data = {__lock = 0, __count = 0, __owner = 0, __kind = 0,
__nusers = 0, {__spins = 0,
__list = {__next = 0x0}}}, __size = '\000' repeats 23 times, __align
= 0}, curr_items = 190673,
total_items
