Github PR: Fix typo in description of `-st` parameter

Dear list! This is an automated relay of the Github pull request: Fix typo in description of `-st` parameter Author: Jorrit Schippers Number of patches: 1 Patch titles: Fix typo in description of `-st` parameter Link: https://github.com/haproxy/haproxy/pull/65 Edit locally:

Re: [PATCH] DOC: fix the entry for hash-balance-factor config option

On Tue, Oct 25, 2016 at 05:04:12PM -0400, Andrew Rodland wrote: > It was accidentally added as "balance-factor". Fix it and > re-alphabetize. merged, thanks Andrew! Willy

[ANNOUNCE] haproxy-1.7-dev5

Hi, HAProxy 1.7-dev5 was released on 2016/10/25. It added 65 new commits after version 1.7-dev4. Things have been calming down since last release, which is quite good. Among the changes I've noticed when preparing this release, the following ones caught my attention: - minimum supported

[PATCH] DOC: fix the entry for hash-balance-factor config option

It was accidentally added as "balance-factor". Fix it and re-alphabetize. Signed-off-by: Andrew Rodland --- doc/configuration.txt | 54 +-- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/doc/configuration.txt

Re: [PATCH] MINOR: build: Allow linking to device-atlas library file

Hi David, On Mon, Oct 10, 2016 at 02:31:03PM +0100, David CARLIER wrote: > Hi willy, > > I think that would be useful to backport it, even when 1.7 will be > out, the 1.6 branch will be still used. Oops sorry I missed your e-mail and discovered that I hadn't pushed Bertrand's patch that I

Re: [PATCH 0/4] Consistent hashing with bounded loads

Hi Andrew, On Tue, Oct 25, 2016 at 12:47:17PM -0400, Andrew Rodland wrote: > Here's a resend of my previous patch, incorporating some changes suggested by > Willy. As my mailer ate my patches last time around, and I'm not completely > sure that it won't do it again, I'm attaching them to this

[PATCH 4/4] MEDIUM: server: Implement bounded-load hash algorithm

The consistent hash lookup is done as normal, then if balancing is enabled, we progress through the hash ring until we find a server that doesn't have "too much" load. In the case of equal weights for all servers, the allowed number of requests for a server is either the floor or the ceil of

[PATCH 3/4] MINOR: server: compute a "cumulative weight" to allow chash balancing to hit its target

For active servers, this is the sum of the eweights of all active servers before this one in the backend, and [srv->cumulative_weight .. srv_cumulative_weight + srv_eweight) is a space occupied by this server in the range [0 .. lbprm.tot_wact), and likewise for backup servers with tot_wbck. This

[PATCH 2/4] MINOR: backend: add hash-balance-factor option for hash-type consistent

0 will mean no balancing occurs; otherwise it represents the ratio between the highest-loaded server and the average load, times 100 (i.e. a value of 150 means a 1.5x ratio), assuming equal weights. Signed-off-by: Andrew Rodland --- doc/configuration.txt| 28

[PATCH 1/4] MINOR: proxy: add 'served' field to proxy, equal to total of all servers'

This will allow lb_chash to determine the total active sessions for a proxy without any computation. Signed-off-by: Andrew Rodland --- include/types/proxy.h | 1 + src/queue.c | 1 + src/stream.c | 2 ++ 3 files changed, 4 insertions(+) diff --git

[PATCH 0/4] Consistent hashing with bounded loads

Hi, Here's a resend of my previous patch, incorporating some changes suggested by Willy. As my mailer ate my patches last time around, and I'm not completely sure that it won't do it again, I'm attaching them to this email as well as sending them inline in the following emails. Thanks,

Re: HAProxy reloads lets old and outdated processes

Hi Pierre, > Apart from that, we exchanged off-list with Willy about the submitted patch. > It seems that if fixes the issue. I now have only one instance bound to the > TCP sockets after the reloads, the others are there just to terminate the > existing connections. And thank you for the quick

RE: HAProxy reloads lets old and outdated processes

Hi, I didn't subscribed to the list and noticed that there was several exchanges on this thread that I didn't read so far. To share a bit more of our context: * we do not reload every 2ms, this was the setting used to be able to reproduce easily and in a short period of time. Our reload

Re: Can I specify a wildcard redirect

Hello Jürgen Thank you for your reply saying its the same line you already have I did this on a single VIP assuming you just wanted to rewrite /de to / and have everything below /de/page-x become /page-x If this is the case it works well and does not produce a redirect loop. Try it out and see

Re: Can I specify a wildcard redirect

Thanks Andrew, That's the same regex that I have in my backend definition. But I also need the ACLs to make sure that the redirect only happens on a specific host and with a specific beginning of a path. Otherwise that would be redirected every time and end up in an infinite loop, doesn't it?

Re: Can I specify a wildcard redirect

Hello Jürgen Sorry for the delay in replying to you. after a little playing I have come up with this single line without an ACL which seems to do what you want. It will redirect http://domain.com/de/this/that/other/dir To http://domain.com/this/that/other/dir reqrep ^([^\ :]*)\ /de/(.*)

Re: Detection of PROXY protocol version and Citrix CIP

Hi Hugo, I'm CCing Bertrand who implemented the netscaler CIP protocol. On Mon, Oct 17, 2016 at 01:36:40PM -0700, Hugo Slabbert wrote: > The PROXY protocol spec specifically indicates that a receiver should not > try to guess whether or not a PROXY protocol header is present[1]: > > > The

Re: Latency spikes

On Mon, Oct 24, 2016 at 11:46:53AM +0300, Dmitry Maslov wrote: > Hello, > > I'm keep digging on this problem and that's what I've found so far: > I have another one frontend/backend pair handled by the same instance, and > it looks like whenever this backend goes slow, everything goes slow. > Why

Re: Issue with windows IE 11 and Edge

On Mon, Oct 24, 2016 at 03:14:59PM +, James Stroehmann wrote: > We have updated our test instance of HAProxy to 1.6.9 but are still able to > reproduce the issue. > > > From: Stroehmann, James > Sent: Friday, October 07, 2016 2:44 PM > To: haproxy@formilux.org > Subject: Issue with windows

Re: HAProxy reloads lets old and outdated processes

Hi Holger, On Tue, Oct 25, 2016 at 12:38:26PM +0200, Holger Just wrote: > Hey Willy, > > Willy Tarreau wrote: > > I absolutely despise systemd and each time I have to work on the > > wrapper I feel like I'm going to throw up. So for me working on this > > crap is a huge pain each time. But I'm

Re: HAProxy reloads lets old and outdated processes

Hey Willy, Willy Tarreau wrote: > I absolutely despise systemd and each time I have to work on the > wrapper I feel like I'm going to throw up. So for me working on this > crap is a huge pain each time. But I'm really fed up with seeing > people having problems in this crazy environment because

Re: http-reuse always, work quite well

On 22/10/2016 08:08 πμ, Willy Tarreau wrote: > Hi Pavlos, > > On Fri, Oct 21, 2016 at 03:01:52PM +0200, Pavlos Parissis wrote: >>> I'm not surprized that always works better, but my point is that if it's >>> much better it can be useful to stay with it, but if it's only 1% better >>> it's not

Re: Can I specify a wildcard redirect

Hi Andrew, just not having luck with this. Here is my rule which is certainly used when e.g. calling https://www.arocom.de/de/team but it doesn't redirect to https://www.arocom.de/team Any idea what's wrong? backend backend_aweb2_https acl r_host hdr(host) -i -n www.arocom.de acl r_path

Re: HAProxy reloads lets old and outdated processes

Hi Jarno, On Tue, Oct 25, 2016 at 11:43:44AM +0300, Jarno Huuskonen wrote: > This is probably a bit off topic, but there's sd_notify call > (and [Service] Type=notify) > where service can notify systemd that it's done starting/reloading > configuration: >

Re: HAProxy reloads lets old and outdated processes

Hi, On Sat, Oct 22, Willy Tarreau wrote: > Another important point, when you say you restart every 2ms, are you > certain you have a way to ensure that everything is completely started > before you issue your signal to kill the old process ? I'm asking because > thanks to the principle that the

Re: HAProxy reloads lets old and outdated processes

On 25/10/2016 01:21 πμ, Willy Tarreau wrote: > Hi guys, > > On Tue, Oct 25, 2016 at 12:42:26AM +0200, Lukas Tribus wrote: >> Not fixing *real world issues* because we don't agree with the use-case or >> there is a design misconception somewhere else is dangerous. We don't have >> to support every

Re: HAProxy reloads lets old and outdated processes

Good morning, Got my coffee ready before I read and reply:-) On 25/10/2016 12:42 πμ, Lukas Tribus wrote: > Hello, > > > Am 24.10.2016 um 22:32 schrieb Pavlos Parissis: >> >> IMHO: Ask the users to not perform reloads every 2miliseconds. It is >> insane. You may spend X hours on this which

Fwd: S FTP + HA PROXY confutation facing one serious issue.

Hello HaProxy Team, *MyObjective*:Client upload file via HaProxy and it will upload in sftp servers *example*: expected this type of configuration in Ha Proxy a.kk.com 192.168.0.1(sftp 1 server ip) b.kk.com 192.168.0.2(sftp