Dynamically Reload Map

[B.R.]

nginx parses configuration as a whole, either on start or on HUP signal.

Your map is part of the configuration (separating it in multiple files does
not change the fast everything is being merged before being statically
interpreted/compiled), thus you need to signal the master process whenever
you change it.

nginx gracefully finishes processing current requests on old workers while
spawning new ones and accepting new connections there.
If performance is an issue, I suggest you have a serious look at how you
dimensioned your infrastructure, since max the double of workers could use
resources at the same time.
If not, you will then have to resort to killing old workers manually.
---
*B. R.*

On Thu, Oct 27, 2016 at 9:44 PM, Cox, Eric S <eric.cox at kroger.com> wrote:

> Is anyone aware of a way to dynamically reload a file when using the MAP
> module without having to reload the server? We have a file that gets
> updated roughly every minute that needs reloaded and it seem that doing a
> reload every minute on the server processes might cause a performance issue?
>
>
>
> Also is anywhere aware of a way to view the current size for the map hash
> tables?
>
>
>
> Thanks
>
> ------------------------------
>
> This e-mail message, including any attachments, is for the sole use of the
> intended recipient(s) and may contain information that is confidential and
> protected by law from unauthorized disclosure. Any unauthorized review,
> use, disclosure or distribution is prohibited. If you are not the intended
> recipient, please contact the sender by reply e-mail and destroy all copies
> of the original message.
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20161030/46cedd20/attachment.html>