Re: 100% cpu , epoll_wait()

[Lukas Tribus]

Hi,


Am 19.04.2016 um 09:39 schrieb Veiko Kukk:

We use haproxy 1.6.3 (latest CentOS 6.7) and experience similar situation after some reloads (-sf). The old haproxy process does not exit and uses 100% cpu, strace showing:

epoll_wait(0, {}, 200, 0)               = 0
epoll_wait(0, {}, 200, 0)               = 0
epoll_wait(0, {}, 200, 0)               = 0
epoll_wait(0, {}, 200, 0)               = 0
epoll_wait(0, {}, 200, 0)               = 0
epoll_wait(0, {}, 200, 0)               = 0

In our case, it was a tcp backend tunnelling rsyslog messages. After restarting local rsyslogd, the load was gone and old haproxy instance exited. It's hard to tell how many reloads it takes to make haproxy go crazy or what is the exact reproducible test. But it does not take hundreds of restart, rather 10-20 (our reloads are not very frequent) to make haproxy go crazy.

Also matches this report from December:
https://www.mail-archive.com/haproxy@formilux.org/msg20772.html



Lukas