> On 13 окт. 2015 г., at 18:47, Willy Tarreau wrote:
>
> Hi Dmitry,
>
> sorry for the delay, I really didn't have time to analyse the config
> you sent me.
>
> A few points below :
>
> On Wed, Oct 07, 2015 at 04:18:20PM +0300, Dmitry Sivachenko wrote:
>> Oct 7 08:33:03 srv1 haproxy[77565]: u
Hi Dmitry,
sorry for the delay, I really didn't have time to analyse the config
you sent me.
A few points below :
On Wed, Oct 07, 2015 at 04:18:20PM +0300, Dmitry Sivachenko wrote:
> Oct 7 08:33:03 srv1 haproxy[77565]: unix:1 [07/Oct/2015:08:33:02.428]
> MT-front MT_RU_EN-back/ 0/1000/-1/-1/10
On Thu, Oct 8, 2015 at 7:15 PM, Dmitry Sivachenko
wrote:
>
> > On 7 окт. 2015 г., at 16:18, Dmitry Sivachenko
> wrote:
> >
> > Hello,
> >
> > I am using haproxy-1.5.14 and sometimes I see the following errors in
> the log:
> >
> > Oct 7 08:33:03 srv1 haproxy[77565]: unix:1 [07/Oct/2015:08:33:02
> On 8 окт. 2015 г., at 15:30, Daren Sefcik wrote:
>
> How about kern.ipc.somaxconn
I have this set to 4096, and when it overflows it prints a line in the log
(Listen queue overflow...)
I have no these errors in logs.
Moreover, connections sitting in socket accept queue are not seen by hapr
How about kern.ipc.somaxconn
On Thu, Oct 8, 2015 at 5:22 AM, Dmitry Sivachenko
wrote:
>
> > On 8 окт. 2015 г., at 3:51, Igor Cicimov
> wrote:
> >
> >
> > The only thing I can think of is you have left net.core.somaxconn = 128,
> try increasing it to 4096 lets say to match your planned capacity
> On 8 окт. 2015 г., at 3:51, Igor Cicimov
> wrote:
>
>
> The only thing I can think of is you have left net.core.somaxconn = 128, try
> increasing it to 4096 lets say to match your planned capacity of 3000
>
I forgot to mention that I am using FreeBSD, I don't think it has similar
sysctl
> On 8 окт. 2015 г., at 11:03, Baptiste wrote:
>
> Hi Dmitry,
>
>
>
> Now the question is why such situation. Simply because your queue
> management is improperly setup (either increase minconn and or
> decrease fullconn) and combined to a server which might be quite slow
> to answer leading
> On 7 окт. 2015 г., at 16:18, Dmitry Sivachenko wrote:
>
> Hello,
>
> I am using haproxy-1.5.14 and sometimes I see the following errors in the log:
>
> Oct 7 08:33:03 srv1 haproxy[77565]: unix:1 [07/Oct/2015:08:33:02.428]
> MT-front MT_RU_EN-back/ 0/1000/-1/-1/1000 503 212 - - sQ--
> 125/
Hi Dmitry,
It says what it says: you configured HAProxy to manage queue to
protect your servers. during your workload, a request remain in queue
for too long (1s) so HAProxy simply return an error.
Now the question is why such situation. Simply because your queue
management is improperly setup (e
On Thu, Oct 8, 2015 at 11:51 AM, Igor Cicimov <
ig...@encompasscorporation.com> wrote:
>
>
> On Thu, Oct 8, 2015 at 12:18 AM, Dmitry Sivachenko
> wrote:
>
>> Hello,
>>
>> I am using haproxy-1.5.14 and sometimes I see the following errors in the
>> log:
>>
>> Oct 7 08:33:03 srv1 haproxy[77565]: u
On Thu, Oct 8, 2015 at 12:18 AM, Dmitry Sivachenko
wrote:
> Hello,
>
> I am using haproxy-1.5.14 and sometimes I see the following errors in the
> log:
>
> Oct 7 08:33:03 srv1 haproxy[77565]: unix:1 [07/Oct/2015:08:33:02.428]
> MT-front MT_RU_EN-back/ 0/1000/-1/-1/1000 503 212 - - sQ--
> 125/124
Hello,
I am using haproxy-1.5.14 and sometimes I see the following errors in the log:
Oct 7 08:33:03 srv1 haproxy[77565]: unix:1 [07/Oct/2015:08:33:02.428] MT-front
MT_RU_EN-back/ 0/1000/-1/-1/1000 503 212 - - sQ-- 125/124/108/0/0 0/28
"POST /some/url HTTP/1.1"
(many similar at one moment)
Co
12 matches
Mail list logo