Graceful shutdown handling in Express - Step-by-Step Execution

Concept Flow - Graceful shutdown handling

Start Server

↓

Server Running

↓

Receive Shutdown Signal

↓

Stop Accepting New Requests

↓

Finish Ongoing Requests

↓

Close Server

↓

Exit Process

The server starts and runs normally. When a shutdown signal arrives, it stops new requests, finishes current ones, closes, and exits.

Execution Sample

Express

const server = app.listen(3000);
process.on('SIGINT', () => {
  server.close(() => {
    process.exit(0);
  });
});

This code starts an Express server and listens for a shutdown signal to close the server gracefully.

Execution Table

Step	Event	Server State	Action Taken	Result
1	Start server	Listening	Server starts listening on port 3000	Server ready for requests
2	Server running	Listening	Handling incoming requests normally	Requests processed
3	Receive SIGINT	Listening	Signal received to shutdown	Prepare to close server
4	Stop accepting new requests	Closing	server.close() called	No new requests accepted
5	Finish ongoing requests	Closing	Wait for current requests to finish	Ongoing requests complete
6	Close server	Closed	Callback from server.close() triggered	Server fully closed
7	Exit process	Closed	process.exit(0) called	Node process exits cleanly

💡 Process exits after server closes and all requests finish

Variable Tracker

Variable	Start	After SIGINT	After server.close()	Final
server.listening	true	true	false	false
process.exitCalled	false	false	false	true

Key Moments - 2 Insights

Why does the server stop accepting new requests but still finish ongoing ones?

When server.close() is called (see step 4 in execution_table), the server stops new connections but keeps existing ones until they finish, ensuring no requests are cut off.

What happens if process.exit() is called before ongoing requests finish?

Calling process.exit() too early would terminate the server immediately, dropping active requests. The code waits for server.close() callback (step 6) before exiting.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the server stop accepting new requests?

A Step 4

B Step 3

C Step 5

D Step 6

💡 Hint

Check the 'Action Taken' column for when server.close() is called.

According to variable_tracker, what is the value of server.listening after server.close()?

A true

B false

C undefined

D null

💡 Hint

Look at the 'After server.close()' column for server.listening.

If process.exit(0) was called immediately after receiving SIGINT (step 3), what would happen?

A Server would close gracefully

B Server would keep accepting requests

C Ongoing requests might be dropped

D Nothing would change

💡 Hint

Refer to key_moments about process.exit() timing.

Concept Snapshot

Graceful shutdown in Express:
- Listen for shutdown signals (e.g., SIGINT)
- Call server.close() to stop new requests
- Wait for ongoing requests to finish
- Exit process after server closes
This prevents dropping active requests during shutdown.

Full Transcript

This visual execution shows how an Express server handles graceful shutdown. The server starts and listens for requests. When a shutdown signal like SIGINT is received, the server stops accepting new requests by calling server.close(). It waits for ongoing requests to finish before closing completely. Finally, the process exits cleanly. Variables like server.listening change from true to false after closing. This ensures no requests are dropped during shutdown.