Hi Willy, I'll try to get it, need some luck :-) --
Best Regards BaiYang baiy...@gmail.com http://baiy.cn **** < END OF EMAIL > **** From: Willy Tarreau Date: 2015-11-22 01:55 To: baiyang CC: Lukas Tribus; haproxy Subject: Re: Re: CPU 100% when waiting for the client timeout Hi Baiyang, On Sun, Nov 22, 2015 at 01:22:42AM +0800, baiyang wrote: > Hi Willy, > > It reproduced again: Ah bad :-/ (...) > I've captured the strace call log successfully this time. You are right, > there are full of epoll_wait and gettimeofday calls. Excellent, thanks for doing this. > Here is the broken request: > Nov 22 01:06:32 WD-G0-SRP1 haproxy[1259]: 2.145.41.3:56014 > [22/Nov/2015:00:50:01.683] https-in~ g0n2/n2 1263/0/0/3/991286 200 84517 - - > CD-- 8/8/1/1/0 0/0 "GET /lib/ext/ext-all.js HTTP/1.1" > > I have been uploaded the total 40 seconds strace log and full haproxy.log to: > http://baiy.cn/tmp/log-1122.rar OK I just downloaded it, thank you. That's interesting, it's not a closed fd that is reported, it's an old timer that is not processed (for a reason I have no idea about) or a task which remains active but not processed, which causes epoll_wait's timeout to remain zero, hence the busy loop. This clearly is an haproxy bug. Did you by chance have the opportunity to retrieve a "show sess all" on the CLI ? I can easily understand that you didn't think about it facing the situation. At least that gives us a few insights about what to look for :-/ Thanks! willy
