toli at webforge.bg
Fri Nov 23 15:53:53 UTC 2012
We have some troubles when nginx have to reload its configuration.
*There is a*control panel and every user which has account may change
its own settings. For example it may add new domain name or change other
option. After that new config files are created and they are sent to the
When there is a new config file master process receives HUP signal and
it loads this new configuration. After the configuration is loaded the
master process starts new workers and waits for old workers to complete
its responses with the end users. Usually there are several slow
connections and old workers can stay alive for a long time.
If there are several new configs for small period of time the number of
workers may become very high and servers' load also gets high values. In
general this is not good for the service.
Do you have any idea how this issue could be solved? Is there different
way to set new config file without a proc*ess *of new workers creation?
Thanks in advance
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx-devel