[PATCH] - ACL for server session rate

Hey List, Considering there is no option yet for maxconnrate for servers (I heard this is on the roadmap), I wrote an ACL to check a backend server session rate which we use to send to an overflow backend to prevent latency responses to our clients (very sensitive latency requirements).

Re: [PATCH] - ACL for server session rate

on to rely on an average rate per server ? Youhave the backend's session rate, you have the number of active servers,so with a divide, you have the average per-server rate. Look at theavg_queue ACL to see how that can be done. I'm sure it will be evenmore useful for you !Regards,Willy

Aggressive Timeouts and Catching 504s

Hey Guys, Had a question about the feasibility of setting aggressive server timeouts then catching and redirecting 504 responses from one backend to another like the following. frontend main bind x.x.x.x:80 acl catch_timeout status ge 504 use_backend secondary if catch_timeout backend

Re: Aggressive Timeouts and Catching 504s

Hey Willy, Willy Tarreau 14 December, 2012 2:45 AM Hi Tait, On Fri, Dec 14, 2012 at 01:28:16AM -0500, Tait Clarridge wrote: Hey Guys, Had a question about the feasibility of setting aggressive server timeouts then catching and redirecting 504 responses from one backend

Re: HAProxy on multi-CPU Hardware

Peter Mellquist 1 February, 2013 12:48 PM Excellent, just what I was looking for!Peter. Just remember that the admin socket will not work as expected with this as it round robins between all the running processes. You would have to size any specific ACLs that deal

Re: HAProxy on multi-CPU Hardware

Peter Mellquist mailto:pemellqu...@gmail.com 1 February, 2013 4:10 PM Thanks for the good input Tait. This would be a code mod but, maybe it would be possible to have different mgmt ports for each process. Maybe baseport+N where N is the process number. I like the IPVS option but keeping it

HTTP Status Code of -1 in the logs

Hello, Recently I noticed log lines with a status code of -1, not sure how long this has been going on for however so not sure if it is a new issue or an older one. In our environment we set strict timeouts as requests (once we get them) need to be processed in 80ms. A cleaned up version

RE: HTTP Status Code of -1 in the logs

Just saw this initial message in its plain text form - that's the last time I send a mailing list message with that mail client. Here is the original message: -- Hello, Recently I noticed log lines with a status code of -1, not sure how

Re: Same servers in multiple backends hit by multiple health checks

Hi Jeff, What you want to use here is track. backend be-1 server1 10.10.10.10:80 check inter 1000 rise 2 fall 2 server2 10.10.10.20:80 check inter 1000 rise 2 fall 2 backend be-2 server1 10.10.10.10:80 track be-1/server1 server2 10.10.10.20:80 track be-1/server1 Tait On Fri,

Re: HTTP Status Code of -1 in the logs

that the calling server (client) library should respect and try to re-establish a connection. We are continuing to dig, just thought I'd update. On Wed, Nov 12, 2014 at 9:28 PM, Tait Clarridge t...@clarridge.ca wrote: Just saw this initial message in its plain text form - that's the last time I send a mailing

[PATCH] MINOR: session: add option to force response on connection/keepalive session errors

Sometimes it is necessary to respond to all requests that HAProxy receives from clients and to not have to wait for the client to retry. This adds an option called http-respond-on-error, where if there is an error in connecting to a server or during the session, the proxy will respond with a 504

Re: [PATCH] MINOR: session: add option to force response on connection/keepalive session errors

On Wed, Dec 10, 2014 at 10:27 AM, Mathias Bogaert mathias.boga...@gmail.com wrote: Would this keep the session open when using errorfile? We have errorfiles that we explicitly set Connection: close for the client to re-establish a new connection. From my limited understanding (still trying to

Re: 1.5.9 crashes every 4 hours, like clockwork

On Thu, Dec 11, 2014 at 10:40 AM, David Adams dr...@yahoo.com wrote: Yes, I am quite sure it's something external to the haproxy process which is somehow interfering with it, but I can't figure out what. As I mentioned, looking at a list of processes before and after haproxy stops doesn't

Re: 1.5.9 crashes every 4 hours, like clockwork

On Thu, Dec 11, 2014 at 12:03 PM, David Adams dr...@yahoo.com wrote: I tried this. I ran it like this: /usr/local/sbin/haproxy -db -f /etc/haproxy/haproxy.cfg which obviously didn't return as the process ran. Then at the crashtime (a few seconds past 17:00), that process terminated and the

Re: nbproc 1 and stats in ADMIN mode?

On Thu, Feb 5, 2015 at 3:44 PM, Pavlos Parissis pavlos.paris...@gmail.com wrote: On 05/02/2015 03:01 μμ, Klavs Klavsen wrote: Hi guys, Just to check.. if I set nbproc to f.ex. 4 - then I understand I need to define 4xstats.. and when I visit the webinterface.. I'll actually only get stats

Re: haproxy rpm

On Mon, Jan 19, 2015 at 8:59 AM, Cohen Galit galit.co...@comverse.com wrote: Hi, I have a problem in packaging the haproxy binary into an rpm. I am using a regular cp command in %install section of spec, but I see that after the copying, the file size is changed and I suspect it is

Re: HAProxy does not write 504 on keep-alive connections

On Tue, Nov 10, 2015 at 7:32 PM, Bryan Talbot wrote: > On Tue, Nov 10, 2015 at 12:04 PM, Laurent Senta > wrote: >> >> Hi there, >> I think there's a bug in how HAProxy handles timeout, that'd be great if >> you can confirm or help me figure out

Re: Observations about reloads and DNS SRV records

On Sun, Jun 10, 2018 at 3:22 AM Baptiste wrote: > > Thanks for giving me this idea! > I wrote a quick and inflexible one here: > https://github.com/bedis/dnsserver > So feel free to contribute to it or write your own :) > > I'm going to use it to troubleshoot the issue you reported. That said, >

Re: Observations about reloads and DNS SRV records

Hey Baptiste, On Sun, Jun 10, 2018 at 3:19 AM Baptiste wrote: > > ==> while writing this mail, I am able to reproduce the issue I think: > - start HAProxy with SRV records > - dump servers state > - update haproxy conf to prevent dns resolution at runtime > - reload haproxy > ==> my servers are

Re: Observations about reloads and DNS SRV records

Hi Baptiste, thanks for the response. On Wed, Jun 6, 2018 at 6:32 PM Baptiste wrote: > > This should not happen and it's a known issue that we're working on. > > Excellent, figured you guys were probably already aware of it. Let me know if I can assist in testing. > > Actually, I tested many

Observations about reloads and DNS SRV records

I've been testing DNS service discovery and the use of SRV records and have a few thoughts on a couple things that I noticed. 1. Reloading with SRV records ignores server-state-file - While this is not a huge deal, it does mean that the backend in question becomes unavailable when the proxy

Re: Observations about reloads and DNS SRV records

On Wed, Jun 6, 2018 at 11:35 AM Aleksandar Lazic wrote: > Hi Tait. > > On 06/06/2018 11:16, Tait Clarridge wrote: > >I've been testing DNS service discovery and the use of SRV records and > have > >a few thoughts on a couple things that I noticed. > > In

Re: Observations about reloads and DNS SRV records

Hey Baptiste, I’ll try it out next week when I get back (currently on vacation) and let you know. Thanks! Tait On Tue., Jul. 3, 2018 at 06:24 Baptiste wrote: > Hi, > > Actually, the problem was deeper than my first thought. > In its current state, statefile and SRV records are simply not