Hi Gabriele,
On Tue, Oct 18, 2016 at 09:40:14PM +0200, Gabriele Cerami wrote:
> Hi,
>
> We're having a problem with version 1.5.14 of haproxy, packaged for
> CentOS 7, but it seems even the code in master is affected.
>
> In situations where bind is not possible (in our case, the address was
> a
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 worth it.
> >
>
> It is way better:-), see Marcin's r
Hi Maciej,
On Fri, Oct 21, 2016 at 03:44:22PM -0700, Maciej Katafiasz wrote:
> There was a similar issue with reloads in Docker that I reported a while
> back: https://www.mail-archive.com/haproxy@formilux.org/msg21485.html . It
> was ultimately tracked down to a faulty Golang compiler version, wh
Hi,
Thank you very much for such a good and useful product. I hope you can help
me in this problem i'm having with HAProxy.
The problem is that when using the *tcp* mode the Lua script dont log/print
the host, path and only the ip is getting logged/printed. If i change the
mode to *http* it print
On 21 October 2016 at 15:33, Willy Tarreau wrote:
>
> On Fri, Oct 21, 2016 at 03:05:55PM +, Pierre Cheynier wrote:
> > First let's clarify again: we are on systemd-based OS (centOS7), so
> reload is
> > done by sending SIGUSR2 to haproxy-systemd-wrapper.
> > Theoretically, this has absolutely
Hi Pierre,
On Fri, Oct 21, 2016 at 03:05:55PM +, Pierre Cheynier wrote:
> First let's clarify again: we are on systemd-based OS (centOS7), so reload is
> done by sending SIGUSR2 to haproxy-systemd-wrapper.
> Theoretically, this has absolutely no relation with our current issue (if I
> understa
Hi Dennis,
On Fri, Oct 21, 2016 at 09:09:39PM +0200, Dennis Jacobfeuerborn wrote:
> So after more experimenting I got things to work properly when I move
> the "limited_path" acl check from the "tcp-request content" directive to
> the "use-backend abuse-warning" directive which accomplishes the sa
On 21.10.2016 18:01, Chad Lavoie wrote:
> Greetings,
>
>
> On 10/21/2016 08:19 AM, Dennis Jacobfeuerborn wrote:
>> Hi,
>> I'm currently experimenting with rate limiting request and while this
>> sort-of works I see an issue where sometimes the stick-table that
>> contains the rate-limiting variab
On 21.10.2016 18:01, Chad Lavoie wrote:
> Greetings,
>
>
> On 10/21/2016 08:19 AM, Dennis Jacobfeuerborn wrote:
>> Hi,
>> I'm currently experimenting with rate limiting request and while this
>> sort-of works I see an issue where sometimes the stick-table that
>> contains the rate-limiting variab
Greetings,
On 10/21/2016 08:19 AM, Dennis Jacobfeuerborn wrote:
Hi,
I'm currently experimenting with rate limiting request and while this
sort-of works I see an issue where sometimes the stick-table that
contains the rate-limiting variables isn't update with every request
allowing multiple requ
Hi,
it's a lot of information, and I don't have time to go into all details
right now, but from a quick read, here are the things I noticed:
- Why nbproc 64? Your CPU has 18 cores (36 w/ HT), so more procs than that
will likely make performance rather worse. HT cores share the cache, so
using 18
Hi Willy,
Thanks for your answer and sorry for my delay.
First let's clarify again: we are on systemd-based OS (centOS7), so reload is
done by sending SIGUSR2 to haproxy-systemd-wrapper.
Theoretically, this has absolutely no relation with our current issue (if I
understand well the way the old
Hi,
again a performance topic.
I did some further testing/benchmarks with ECC and nbproc >1. I was
testing on a "E5-2697 v4" and the first thing I noticed was that HAProxy
has a fixed limit of 64 for nbproc. So the setup:
HAProxy server with the mentioned E5:
global
user haproxy
group
On 21/10/2016 08:14 πμ, Willy Tarreau wrote:
> Hi Pavlos,
>
> On Wed, Oct 19, 2016 at 08:28:34AM +0200, Pavlos Parissis wrote:
>>> That's really great, thanks for the feedback. Have you tried the other
>>> http-reuse options ?
>>
>> A workmate did the experimentation on http-reuse and I only know
Hi,
I'm currently experimenting with rate limiting request and while this
sort-of works I see an issue where sometimes the stick-table that
contains the rate-limiting variables isn't update with every request
allowing multiple requests to succeed even if they shouldn't.
I attached the configuratio
15 matches
Mail list logo