Hot answers tagged haproxy
The TCP RTO (receive timeout) starts at three seconds. (RFC 1122) If a transmitted packet hasn't had an acknowledgement returned in that time, then it's assumed to be lost and retransmitted. This is almost certainly what the author is referring to. (Note that the RTO gets tuned up or down dynamically by various algorithms, outside the scope of this ...
Maybe it helps if you add an explicit URL to your httpchk - per default it uses an http OPTION on /. Also you have to add the "check" keyword to your host definitions (http://haproxy.1wt.eu/download/1.3/doc/haproxy-en.txt section 3.1) backend app timeout server 50000ms mode http balance roundrobin option httpchk HEAD /some/valid/url ...
You might be able to get this to work by checking hdr_dom (https://code.google.com/p/haproxy-docs/wiki/MatchingLayer7) instead of hdr: acl is_api hdr_dom(host) -i api.example.com acl is_app hdr_dom(host) -i app.example.com Just be careful because I believe this would also match things like "otherstuff.api.example.com".
We experienced the same issue today. I'm not sure about #1 but I believe the second problem is that the reconnection delay is never reset in amqp_listener.py and should be done so before the protocol is built in buildProtocol. I submitted a pull request here: https://github.com/graphite-project/carbon/pull/102. Hope this helps. Before the change (exceptions ...
Only top voted, non community-wiki answers of a minimum length are eligible