MSK · UTC+3 · 18 Nov 2026note

← all notes

A reload is not a restart

nginx20 Oct 2026 · 4 min read

Nginx reloads are described as zero-downtime, and they usually are — which is exactly why the exceptions are confusing. Understanding what a reload actually does makes the difference between a five-second change and a five-minute outage.

What happens on reload

The master process re-reads the configuration, starts new worker processes with it, and asks the old workers to finish their current connections and exit. Listening sockets are inherited, so no connection is refused.

old workers · draining new workers · accepting reload
Existing requests finish on the old workers; new connections land on the new ones. If a request never finishes, its worker never exits.

Where “zero downtime” stops being true

The check I always run

nginx -t && systemctl reload nginx
sleep 2
ss -tnp | grep nginx | wc -l
ps -o pid,etime,cmd -C nginx

If old workers are still there after a minute with no active connections, something is holding them — and that something is usually a client that never closed a stream.