Hi, guys! Recently, we use haproxy in our projects. After a month of work, we found our debian7.0 x86 system became strange.
OS: debian 7.0 CPU: Quad-Core AMD Opteron(tm) Processor 2380 x2 Memory: 8GB HA-Proxy version 1.4.22 2012/08/09 Copyright 2000-2012 Willy Tarreau <[email protected]> Build options : TARGET = linux2628 CPU = native CC = gcc CFLAGS = -m64 -march=x86-64 -O2 -march=native -g -fno-strict-aliasing OPTIONS = USE_LINUX_TPROXY=1 USE_NETFILTER=1 USE_REGPARM=1 USE_STATIC_PCRE=1 Default settings : maxconn = 2000, bufsize = 16384, maxrewrite = 8192, maxpollevents = 200 Encrypted password support via crypt(3): yes Available polling systems : sepoll : pref=400, test result OK epoll : pref=300, test result OK poll : pref=200, test result OK select : pref=150, test result OK Total: 4 (4 usable), will use sepoll. top - 18:41:05 up 79 days, 2:33, 4 users, load average: 1.24, 1.38, 1.35 Tasks: 135 total, 1 running, 134 sleeping, 0 stopped, 0 zombie %Cpu(s): 2.1 us, 8.9 sy, 0.0 ni, 77.3 id, 0.0 wa, 0.0 hi, 11.7 si, 0.0 st KiB Mem: 8262492 total, 7419548 used, 842944 free, 22184 buffers KiB Swap: 8984572 total, 352 used, 8984220 free, 1820292 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 25280 root 20 0 924m 635m 848 S 36.3 7.9 17243:00 /usr/local/sbin/haproxy -f /usr/local/etc/node2.haproxy.cfg 25279 root 20 0 669m 457m 832 S 21.0 5.7 11468:07 /usr/local/sbin/haproxy -f /usr/local/etc/node2.haproxy.cfg 25278 root 20 0 485m 330m 832 S 16.3 4.1 7484:49 /usr/local/sbin/haproxy -f /usr/local/etc/node2.haproxy.cfg 25281 root 20 0 511m 336m 832 S 11.3 4.2 5265:05 /usr/local/sbin/haproxy -f /usr/local/etc/node2.haproxy.cfg 25277 root 20 0 338m 227m 832 S 8.3 2.8 4287:26 /usr/local/sbin/haproxy -f /usr/local/etc/node2.haproxy.cfg 25276 root 20 0 239m 159m 832 S 5.3 2.0 2554:31 /usr/local/sbin/haproxy -f /usr/local/etc/node2.haproxy.cfg 25275 root 20 0 217m 135m 832 S 3.3 1.7 1572:01 /usr/local/sbin/haproxy -f /usr/local/etc/node2.haproxy.cfg 25274 root 20 0 151m 100m 832 S 2.7 1.2 1158:03 /usr/local/sbin/haproxy -f /usr/local/etc/node2.haproxy.cfg root@frontenda:~# vmstat 1 procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu---- r b swpd free buff cache si so bi bo in cs us sy id wa 0 0 352 815364 22184 1820104 0 0 0 0 1 0 2 14 84 0 0 0 352 816184 22184 1820104 0 0 0 0 85662 46301 3 21 76 0 0 0 352 816308 22184 1820104 0 0 0 18 85913 44570 2 21 76 1 0 0 352 816488 22184 1820104 0 0 0 0 87543 44162 2 21 77 0 we found there just 800M free Memory and cache 1.8GB memory.But the total RAM is 8GB.How can my system eat so many memory for cache? And there is another problem in my system.There is the dmesg [6711815.708019] TCP: Peer 10.21.3.1:53820/80 unexpectedly shrunk window 652446854:652454102 (repaired) [6746057.912030] TCP: Peer 10.18.4.1:59366/80 unexpectedly shrunk window 1558303990:1558311259 (repaired) [6843147.172024] TCP: Peer 10.2.3.4:61158/80 unexpectedly shrunk window 537264444:537265217 (repaired) [6843147.916019] TCP: Peer 192.168.211.1:61158/80 unexpectedly shrunk window 537264444:537265217 (repaired) ……. There are my this messages in my dmesg. I googled, which says this is a serious problem. But i don't know what happened for the haproxy?
