Hi Willy,
Here is another issue seen today with the current dev branch [tests were also
made after pulling recent commit 3bcc2699b].
Since 0c026f49e, when a server status is set to DOWN and option redispatch is
enabled, the haproxy process hits 100% CPU.
Even more, with the latest commits, if haproxy is compiled with DEBUG_FULL, it
will simply segfault.
Here is the minimal configuration for the test:
listen crash
bind :9000
option redispatch
server non-existent 127.0.0.1:9999 check
I'll look at it later if nobody has fixed it in the mean time ;)
Cyril
