Re: nginx reverse proxy causing TCP queuing spikes
>> I do think this is related to 'proxy_read_timeout 60m;' leaving too >> many connections open. Can I somehow allow pages to load for up to >> 60m but not bog my server down with too many connections? > > Pardon me, but why on earth do you have an environment in which an HTTP > request can take an hour? That seems like a serious abuse of the protocol. > > Keeping an HTTP request open means keeping the associated TCP connection open > as well. If you have connections open for an hour, you're probably going to > run into concurrency issues. I don't actually need 60m but I do need up to about 20m for some backend administrative processes. What is the right way to solve this problem? I don't think I can speed up the processes. - Grant ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: nginx reverse proxy causing TCP queuing spikes
> I do think this is related to 'proxy_read_timeout 60m;' leaving too > many connections open. Can I somehow allow pages to load for up to > 60m but not bog my server down with too many connections? Pardon me, but why on earth do you have an environment in which an HTTP request can take an hour? That seems like a serious abuse of the protocol. Keeping an HTTP request open means keeping the associated TCP connection open as well. If you have connections open for an hour, you're probably going to run into concurrency issues. ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: nginx reverse proxy causing TCP queuing spikes
>> I've been struggling with http response time slowdowns and >> corresponding spikes in my TCP Queuing graph in munin. I'm using >> nginx as a reverse proxy to apache which then hands off to my backend, >> and I think the proxy_read_timeout line in my nginx config is at least >> contributing to the issue. Here is all of my proxy config: >> >> proxy_read_timeout 60m; >> proxy_pass http://127.0.0.1:8080; >> >> I think this means I'm leaving connections open for 60 minutes after >> the last server response which sounds like a bad thing. However, some >> of my admin pages need to run for a long time while they wait for the >> server-side stuff to execute. I only use the proxy_read_timeout >> directive on my admin locations and I'm experiencing the TCP spikes >> and http slowdowns during the exact hours that the admin stuff is in >> use. > > > It turns out this issue was due to Odoo which also runs behind nginx > in a reverse proxy configuration on my machine. Has anyone else had > that kind of trouble with Odoo? I do think this is related to 'proxy_read_timeout 60m;' leaving too many connections open. Can I somehow allow pages to load for up to 60m but not bog my server down with too many connections? - Grant ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: nginx reverse proxy causing TCP queuing spikes
It is most probably a question more suitable to some Odoo ML. --- *B. R.* On Sun, Sep 25, 2016 at 2:50 AM, Grant wrote: > > I've been struggling with http response time slowdowns and > > corresponding spikes in my TCP Queuing graph in munin. I'm using > > nginx as a reverse proxy to apache which then hands off to my backend, > > and I think the proxy_read_timeout line in my nginx config is at least > > contributing to the issue. Here is all of my proxy config: > > > > proxy_read_timeout 60m; > > proxy_pass http://127.0.0.1:8080; > > > > I think this means I'm leaving connections open for 60 minutes after > > the last server response which sounds like a bad thing. However, some > > of my admin pages need to run for a long time while they wait for the > > server-side stuff to execute. I only use the proxy_read_timeout > > directive on my admin locations and I'm experiencing the TCP spikes > > and http slowdowns during the exact hours that the admin stuff is in > > use. > > > It turns out this issue was due to Odoo which also runs behind nginx > in a reverse proxy configuration on my machine. Has anyone else had > that kind of trouble with Odoo? > > - Grant > > ___ > nginx mailing list > nginx@nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx > ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: nginx reverse proxy causing TCP queuing spikes
> I've been struggling with http response time slowdowns and > corresponding spikes in my TCP Queuing graph in munin. I'm using > nginx as a reverse proxy to apache which then hands off to my backend, > and I think the proxy_read_timeout line in my nginx config is at least > contributing to the issue. Here is all of my proxy config: > > proxy_read_timeout 60m; > proxy_pass http://127.0.0.1:8080; > > I think this means I'm leaving connections open for 60 minutes after > the last server response which sounds like a bad thing. However, some > of my admin pages need to run for a long time while they wait for the > server-side stuff to execute. I only use the proxy_read_timeout > directive on my admin locations and I'm experiencing the TCP spikes > and http slowdowns during the exact hours that the admin stuff is in > use. It turns out this issue was due to Odoo which also runs behind nginx in a reverse proxy configuration on my machine. Has anyone else had that kind of trouble with Odoo? - Grant ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
nginx reverse proxy causing TCP queuing spikes
I've been struggling with http response time slowdowns and corresponding spikes in my TCP Queuing graph in munin. I'm using nginx as a reverse proxy to apache which then hands off to my backend, and I think the proxy_read_timeout line in my nginx config is at least contributing to the issue. Here is all of my proxy config: proxy_read_timeout 60m; proxy_pass http://127.0.0.1:8080; I think this means I'm leaving connections open for 60 minutes after the last server response which sounds like a bad thing. However, some of my admin pages need to run for a long time while they wait for the server-side stuff to execute. I only use the proxy_read_timeout directive on my admin locations and I'm experiencing the TCP spikes and http slowdowns during the exact hours that the admin stuff is in use. - Grant ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
