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.

Practice

1. What is the main purpose of implementing graceful shutdown in an Express server?

easy

A. To allow the server to finish handling current requests before stopping

B. To restart the server automatically after a crash

C. To speed up server startup time

D. To block all incoming requests permanently

Solution

1. Step 1: Understand graceful shutdown concept

   Graceful shutdown means the server stops accepting new requests but finishes processing ongoing ones.

2. Step 2: Identify the purpose in Express context

   In Express, this prevents dropping requests abruptly when stopping the server.

3. Final Answer:

   To allow the server to finish handling current requests before stopping -> Option A

4. Quick Check:

   Graceful shutdown = finish requests before stop [OK]

Hint: Graceful shutdown means finishing requests before exit [OK]

Common Mistakes:

• Thinking it restarts the server automatically
• Confusing it with startup speed
• Believing it blocks all requests permanently

2. Which of the following is the correct way to start listening for a shutdown signal in an Express app?

easy

A. express.shutdown('SIGINT', () => { /* shutdown code */ });

B. server.listen('SIGINT', () => { /* shutdown code */ });

C. app.shutdown('SIGINT', () => { /* shutdown code */ });

D. process.on('SIGINT', () => { /* shutdown code */ });

Solution

1. Step 1: Identify how Node.js listens for signals

   Node.js uses process.on('signal', callback) to listen for OS signals like SIGINT.

2. Step 2: Confirm Express does not have shutdown method

   Express app or server does not have shutdown methods; signal handling is done on process.

3. Final Answer:

   process.on('SIGINT', () => { /* shutdown code */ }); -> Option D

4. Quick Check:

   Signal listening uses process.on [OK]

Hint: Use process.on to catch shutdown signals [OK]

Common Mistakes:

• Using server.listen for signals
• Calling shutdown on app or express object
• Confusing signal handling with server methods

3. Consider this Express server code snippet:

const express = require('express');
const app = express();
const server = app.listen(3000);

process.on('SIGTERM', () => {
  server.close(() => {
    console.log('Server closed');
  });
});

console.log('Server running');

What will happen when the process receives a SIGTERM signal?

medium

A. The server stops accepting new requests and logs 'Server closed' after finishing current requests

B. The server immediately crashes without logging anything

C. The server ignores the SIGTERM signal and keeps running

D. The server restarts automatically

Solution

1. Step 1: Analyze signal handler code

   On SIGTERM, server.close() is called with a callback that logs 'Server closed'.

2. Step 2: Understand server.close behavior

   server.close stops new connections but waits for ongoing requests to finish before calling the callback.

3. Final Answer:

   The server stops accepting new requests and logs 'Server closed' after finishing current requests -> Option A

4. Quick Check:

   SIGTERM triggers server.close with log after finish [OK]

Hint: server.close waits for requests before callback [OK]

Common Mistakes:

• Assuming immediate crash on SIGTERM
• Thinking server restarts automatically
• Believing server ignores SIGTERM

4. This code attempts graceful shutdown but has a bug:

const express = require('express');
const app = express();
const server = app.listen(3000);

process.on('SIGINT', () => {
  server.close();
  console.log('Server closed');
  process.exit(0);
});

What is the problem with this shutdown code?

medium

A. It should call app.close() instead of server.close()

B. It calls process.exit(0) immediately, not waiting for server.close to finish

C. It does not listen on the correct port

D. It uses SIGINT instead of SIGTERM, which is invalid

Solution

1. Step 1: Understand server.close asynchronous behavior

   server.close is asynchronous and takes a callback to run after closing.

2. Step 2: Identify premature exit call

   process.exit(0) is called immediately after server.close without waiting, so server may not close properly.

3. Final Answer:

   It calls process.exit(0) immediately, not waiting for server.close to finish -> Option B

4. Quick Check:

   Must wait for server.close callback before exit [OK]

Hint: Wait for server.close callback before exiting process [OK]

Common Mistakes:

• Thinking SIGINT is invalid signal
• Confusing app.close with server.close
• Ignoring asynchronous nature of server.close

5. You want to implement graceful shutdown in an Express app that also uses a database connection. Which approach correctly ensures both server and database close properly before exiting?

hard

A. Call process.exit() immediately on SIGINT, then close server and database asynchronously

B. Close database connection first, then call server.close(), ignoring process signals

C. Listen for SIGINT, call server.close(), then close database in server.close callback, finally call process.exit()

D. Restart the server automatically on SIGINT without closing connections

Solution

1. Step 1: Handle SIGINT signal properly

   Listen for SIGINT to start graceful shutdown process.

2. Step 2: Close server and then database sequentially

   Call server.close() to finish requests, then in its callback close the database connection.

3. Step 3: Exit process after all resources are closed

   Call process.exit() only after both server and database are closed to avoid abrupt termination.

4. Final Answer:

   Listen for SIGINT, call server.close(), then close database in server.close callback, finally call process.exit() -> Option C

5. Quick Check:

   Shutdown sequence: server.close -> db.close -> exit [OK]

Hint: Close server then DB before exiting on signal [OK]

Common Mistakes:

• Exiting process before closing resources
• Ignoring database closure
• Restarting server instead of shutting down