Well, all the problems, the original one that we hit a couple of months ago
and the current one are related to one thing: Apache expects some
request/response to be read by the downstream haproxy ( and its backends)
which refuse to do it due to some error condition and instead sends back a
error
On Tuesday 20 of September 2011 02:02:27 Dean Hiller wrote:
We are running haproxy at amazon and running some load tests and seem to be
hitting some bottleneck between haproxy and webservers or haproxy itself.
How can you tell when haproxy is maxed out? Will cpu hit 100% or is it
some other
Hi,
What do you mean when you say running -c?
Here's my config file.
Thanks for your help.
Christophe
global
log 192.168.0.2 local0
log 127.0.0.1 local1 notice
maxconn 10240
defaults
logglobal
option dontlognull
retries2
timeout client 35s
timeout server 35s
timeout connect 5s
We have various services that expose internal errors I am trying to
masquerade with haproxy.
The only keyword I can find that can look at the result at all is
rspdeny. The documentation says
It is easier, faster and more powerful to use ACLs to write access
policies. Rspdeny should be avoided in
4 matches
Mail list logo