6 ms·
This doesn't work well for modern websites using push-style updates, e.g. via websockets. Old nginx processes might never close after the reload, as connections
by onestone 9y ago
This doesn't work well for modern websites using push-style updates, e.g. via websockets. Old nginx processes might never close after the reload, as connections are very long-lived. If reloads happen often this leads to memory exhaustion. So this is a bad solution to rely on.
- ploxiln 9y agoWebsockets are indeed a complication, I'm guessing for haproxy also. But it seems nginx has a recently added feature which can fix this: https://nginx.org/en/docs/ngx_core_module.html#worker_shutdown_timeout https://nginx.org/en/docs/ngx_core_module.html#worker_shutdo...