Got it, thank you for the confirmation!
On Wed, Nov 15, 2023, 10:30 PM Willy Tarreau wrote:
> Hello,
>
> On Wed, Nov 15, 2023 at 05:30:06PM -0600, JJ Graham wrote:
> > Hi there,
> >
> > Does fullconn do anything in backends where minconn/maxconn are n
Hello,
On Wed, Nov 15, 2023 at 05:30:06PM -0600, JJ Graham wrote:
> Hi there,
>
> Does fullconn do anything in backends where minconn/maxconn are not used on
> any server? The documentation and previous answers to similar questions
> seem to imply the answer is "no" but
Hi there,
Does fullconn do anything in backends where minconn/maxconn are not used on
any server? The documentation and previous answers to similar questions
seem to imply the answer is "no" but the fact that it gets set to a default
value ("10% of the sum of the maxconns o
Lukas Tribus wrote:
[dd]
>
> > It would be nice however to understand minconn/fullconn too. If a
> > backend has several servers with identical minconn, maxconn and weight,
> > what's the point of having minconn? The load will be always distributed
> > eve
time?
> I suppose the TCP connection with the client is reset?
Yes, that's the only choice.
>
> >
> > See:
> >
> > timeout queue
> > https://cbonte.github.io/haproxy-dconv/2.2/configuration.html#4.2-timeout%20queue
> >
> > maxconn
> > https://cb
tps://cbonte.github.io/haproxy-dconv/2.2/configuration.html#4.2-timeout%20queue
>
> maxconn
> https://cbonte.github.io/haproxy-dconv/2.2/configuration.html#5.2-maxconn
>
>
> I really suggest you ignore minconn and fullconn, and focus on maxconn
> instead. The latter is a must-h
nection timeout).
See:
timeout queue
https://cbonte.github.io/haproxy-dconv/2.2/configuration.html#4.2-timeout%20queue
maxconn
https://cbonte.github.io/haproxy-dconv/2.2/configuration.html#5.2-maxconn
I really suggest you ignore minconn and fullconn, and focus on maxconn
instead. The latter is
r
> maxconn 1
> default_backend foo
>
> backend foo
> server server1 server1: minconn 10 maxconn 100 weight 100
> server server2 server2: minconn 10 maxconn 100 weight 100
>
>
> This configuration will set the auto
fullconn=1000 to the
backend "foo", correct?
"maxconn 100" is still a hard limit, correct?
So, when there happen to be 500 connections to the backend "foo", 200
of them will be served by server1 and server2, what will happen to the
other 300 connections?
The same can b
*From:* Jerome Magnin [mailto:jmag...@haproxy.com]
*Sent:* Tuesday, July 16, 2019, 10:19 EDT
*To:* Patrick Hemmer
*Cc:* Pavlos Parissis , haproxy@formilux.org
*Subject:* fullconn not working
Hi Patrick,
On Tue, Jul 16
formilux.org
> *Cc:* Patrick Hemmer
> *Subject:* fullconn not working
>
> > On Παρασκευή, 28 Ιουνίου 2019 5:50:48 Μ.Μ. CEST Patrick Hemmer wrote:
> > > I'm trying to get fullconn working, and can't seem to do so. I dunno if
> > > it's a bug, or if it's my
*From:* Pavlos Parissis [mailto:pavlos.paris...@gmail.com]
*Sent:* Tuesday, July 16, 2019, 09:32 EDT
*To:* haproxy@formilux.org
*Cc:* Patrick Hemmer
*Subject:* fullconn not working
On Παρασκευή, 28 Ιουνίου 2019 5:50:48
On Παρασκευή, 28 Ιουνίου 2019 5:50:48 Μ.Μ. CEST Patrick Hemmer wrote:
> I'm trying to get fullconn working, and can't seem to do so. I dunno if
> it's a bug, or if it's my understanding that's wrong.
> Basically my goal is to prevent the cumulative total of all connections
> to
*From:* Patrick Hemmer [mailto:hapr...@stormcloud9.net]
*Sent:* Friday, June 28, 2019, 11:50 EDT
*To:* HAProxy
*Subject:* fullconn not working
I'm trying to get fullconn working, and can't seem to do so. I dunno
if it's
I'm trying to get fullconn working, and can't seem to do so. I dunno if
it's a bug, or if it's my understanding that's wrong.
Basically my goal is to prevent the cumulative total of all connections
to all servers in a pool from exceeding a certain value.
For example I might have 10 servers, each
Hi,
On my understanding, "globle.maxconn", "backend.maxconn", "backend.fullconn"
and "stick-table" all use the per-process semantics, right?
E.g.: If nbproc = 9 and we have this directive in a frontend or backend:
"stick-table type ip size 1m expire 1m store
Well, not at all :-)
So, minconn is an upper limit for incoming connections , is right ?
And maxconn will be the new upper limit for incoming connections when the
number
of connection ( concurrent ? ) on the backend is equal to fullconn. is
right ?
And what does it happen if the number
Hello:
I'm reading about fullconn parameter in
https://code.google.com/p/haproxy-docs/wiki/fullconn
and I don't get the example
# The servers will accept between 100 and 1000 concurrent connections each
# and the maximum of 1000 will be reached when the backend reaches 1
# connections
Hi,
Long time nobody asked for fullconn information :)
fullconn allows HAProxy to manage connections on your server.
It means that HAProxy will increase connection opened on the server,
from minconn to maxconn. And maxconn will be reached when the number
of connection on the backend is equal
generally are even more confused. Let's try again...
First of all, fullconn confuses me, and this example doesn't help
Example :
# The servers will accept between 100 and 1000 concurrent connections
each
# and the maximum of 1000 will be reached when the backend reaches 1
Hello,
I've been going through haproxy in depth recently, but I can't quite
figure out the details with full, min, and maxconn.
First of all, fullconn confuses me, and this example doesn't help
Example :
# The servers will accept between 100 and 1000 concurrent connections each
21 matches
Mail list logo
