Re: worker_connections are not enough, reusing connections with idle workers

2022-06-07 Thread Sergey A. Osokin
Hi Roger, I've forgotten to ask about the nginx version, so as Maxim Dounin recommended, please upgrade to the recent stable version 1.22.0, https://nginx.org/en/linux_packages.html#Ubuntu On Tue, Jun 07, 2022 at 02:42:23PM -0700, Roger Fischer wrote: > Here are the additional details: > > $ una

Re: worker_connections are not enough, reusing connections with idle workers

2022-06-07 Thread Maxim Dounin
Hello! On Tue, Jun 07, 2022 at 01:18:36PM -0700, Roger Fischer wrote: > My assumption is that the client requests will be distributed > over the 24 worker processes. So no individual worker should > come anywhere close to 1000 connections. > > But when I look at the process stats for the worke

Re: worker_connections are not enough, reusing connections with idle workers

2022-06-07 Thread Roger Fischer
Here are the additional details: $ uname -a Linux a002 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.6 LTS" $ cat /etc/os-rel

Re: worker_connections are not enough, reusing connections with idle workers

2022-06-07 Thread Sergey A. Osokin
On Tue, Jun 07, 2022 at 01:18:36PM -0700, Roger Fischer wrote: > > We are simulating 1000 clients. Some get cache hits, and some go upstream. So > there are more than 1000 connections. > > We have 24 workers running, each configured: events { worker_connections > 1024; } > > We are seeing the

Re: worker_connections are not enough, reusing connections with idle workers

2022-06-07 Thread Roger Fischer
Thanks, Sergey. We are simulating 1000 clients. Some get cache hits, and some go upstream. So there are more than 1000 connections. We have 24 workers running, each configured: events { worker_connections 1024; } We are seeing the following errors from nginx: [warn] 21151#21151: 1024 worker_c

Re: How to disable http v2

2022-06-07 Thread Peter Volkov
On Tue, 7 Jun 2022 at 14:15, Sergey Kandaurov wrote: > > On 7 Jun 2022, at 13:41, Peter Volkov wrote: > > After we enabled HTTP/2 in nginx some old software started to fail. So > we would like to have HTTP v2 enabled in general but disabled for some > specific IP:PORT. I've tried two listen dire

Re: How to disable http v2

2022-06-07 Thread Sergey Kandaurov
> On 7 Jun 2022, at 13:41, Peter Volkov wrote: > > Hi. > > After we enabled HTTP/2 in nginx some old software started to fail. So we > would like to have HTTP v2 enabled in general but disabled for some specific > IP:PORT. I've tried two listen directives in server block: > > listen I

How to disable http v2

2022-06-07 Thread Peter Volkov
Hi. After we enabled HTTP/2 in nginx some old software started to fail. So we would like to have HTTP v2 enabled in general but disabled for some specific IP:PORT. I've tried two listen directives in server block: listen IP:443 ssl http2; listen IP:1443 ssl; The problem is that on both p