Configuration reload vs restart in Nginx - Visual Side-by-Side Comparison

Process Flow - Configuration reload vs restart

Start

↓

Change config file

↓

Send reload signal

↓

Master reloads config

↓

Worker processes reload

↓

Nginx running with new config

↓

End

Shows the flow of updating nginx configuration by either reloading or restarting the service.

Execution Sample

Nginx

sudo nginx -s reload
sudo systemctl restart nginx

Reload applies new config without stopping nginx; restart stops and starts nginx service.

Process Table

Step	Action	Process State Before	Process State After	Effect
1	Change nginx.conf file	nginx running with old config	nginx running with old config	Config file updated on disk
2	Run 'sudo nginx -s reload'	Master and workers running old config	Master reloads config, workers reload gracefully	New config applied without downtime
3	Check nginx processes	Master and workers running new config	Master and workers running new config	Nginx serving with updated config
4	Run 'sudo systemctl restart nginx'	Master and workers running new config	All nginx processes stopped	Nginx service stopped
5	Systemctl starts nginx	No nginx processes running	Master and workers started with new config	Nginx restarted with new config
6	Check nginx processes	Master and workers running new config	Master and workers running new config	Nginx serving with updated config
7	End	Nginx running with new config	Nginx running with new config	Configuration update complete

💡 Process ends with nginx running the new configuration after reload or restart

Status Tracker

Variable	Start	After reload	After restart	Final
nginx_process_state	running with old config	running with new config (graceful reload)	stopped then running with new config	running with new config
config_file	old config	new config on disk	new config on disk	new config on disk

Key Moments - 3 Insights

Why does reload not stop nginx processes completely?

Reload sends a signal to master process to reload config gracefully, so worker processes finish current requests before restarting, as shown in execution_table step 2.

What happens to nginx processes during restart?

Restart stops all nginx processes completely and then starts them fresh, causing a brief downtime, as shown in execution_table steps 4 and 5.

Does reload cause downtime?

No, reload applies new config without downtime by gracefully restarting workers, unlike restart which stops nginx temporarily.

Visual Quiz - 3 Questions

Look at the execution_table, what is the nginx process state immediately after 'sudo nginx -s reload'?

A Master and workers running new config

B All nginx processes stopped

C Master and workers running old config

D No nginx processes running

💡 Hint

Check execution_table row 2 under 'Process State After'

At which step does nginx experience downtime?

A Step 2 - reload

B Step 1 - config change

C Step 4 - restart stop

D Step 3 - check processes

💡 Hint

Look at execution_table step 4 where all nginx processes are stopped

If you want zero downtime when applying new config, which command should you use?

A sudo systemctl restart nginx

B sudo nginx -s reload

C sudo nginx -s stop

D sudo systemctl stop nginx

💡 Hint

Refer to execution_table step 2 and key_moments about graceful reload

Concept Snapshot

Reload vs Restart in nginx:
- Reload (nginx -s reload): applies new config gracefully without stopping service.
- Restart (systemctl restart nginx): stops and starts nginx, causing brief downtime.
- Reload sends signal to master; workers reload without dropping connections.
- Restart fully stops all processes before starting again.
- Use reload for config changes to avoid downtime.

Full Transcript

This visual execution shows how nginx configuration changes are applied by either reloading or restarting. First, the config file is changed on disk. Reload sends a signal to the nginx master process to reload the configuration gracefully, allowing worker processes to finish current requests before restarting. This means nginx continues serving without downtime. Restart stops all nginx processes completely and then starts them fresh, causing a brief downtime. The execution table traces each step, showing process states before and after reload or restart. Variable tracking shows nginx process states and config file status across steps. Key moments clarify why reload avoids downtime and restart causes it. The quiz tests understanding of process states and downtime moments. The snapshot summarizes the key differences and commands for reload vs restart.