Poor performance when loading huge number of server section

Hi there, I got a problem when using nginx as a reverse proxy. Configurations using per server policy to set upstream host. Nginx spends significant time loading config files as while as virtual server inscreased to a large number. Here's a rough statistics: | server sections | load time(sec) |

Re: Changing Nginx keep-alive behavior based on error response of proxied server

Any ideas/suggestions related to forcing a client connection close on certain errors from proxied server? Please refer my previous post for details. Thanks. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,241653,241721#msg-241721 ___ nginx ma

Re: Worker process is not getting killed , when master is killed using -9

On 2013-08-08 at 06:29 +, Vivek Goel wrote: > I am facing one problem with nginx. I am waiting for nginx to stop withing > 30 seconds. If it is not getting stopped, I am firing command to kill > master process using > pkill -9 > > But, Killing master is not killing the worker process. Due to

upstream max_fails disable

Hi I'm using the upstream module - with sole purpose to enable keepalives to my backend I don't want to use any of the other features, I only have 1 server in the upstream {} Does that mean max_fails is still being used? (defaults to 1?) and fail_timeout etc..? they both have default values Wh