Graceful shutdown on errors in Node.js - Performance & Optimization

Performance: Graceful shutdown on errors

HIGH IMPACT

This affects server responsiveness and resource cleanup during error conditions, impacting user experience and server stability.

Handling unexpected errors to avoid server crashes and blocked requests

Node.js

process.on('uncaughtException', (err) => {
  console.error('Uncaught Exception:', err);
  server.close(() => {
    // cleanup resources here
    process.exit(1);
  });
});

Stops accepting new requests and cleans up resources before exit, preventing request blocking and memory leaks.

📈 Performance GainReduces INP spikes by quickly freeing resources and avoiding stuck requests.

Handling unexpected errors to avoid server crashes and blocked requests

Node.js

process.on('uncaughtException', (err) => {
  console.error('Uncaught Exception:', err);
  // No shutdown or cleanup, server keeps running
});

Server continues running in an unstable state, causing unpredictable behavior and potential request blocking.

📉 Performance CostBlocks new requests indefinitely, increasing INP and causing poor user experience.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No graceful shutdown on error	N/A	N/A	N/A	[X] Bad
Graceful shutdown with cleanup	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Graceful shutdown does not directly affect browser rendering but impacts server response times and availability, which influence interaction responsiveness (INP).

→Server Response Time

→Request Handling

→Resource Cleanup

⚠️ BottleneckRequest Handling when server is unstable or blocked

Core Web Vital Affected

INP

This affects server responsiveness and resource cleanup during error conditions, impacting user experience and server stability.

Optimization Tips

1Always stop accepting new requests before shutting down on error.

2Clean up resources like database connections to prevent leaks.

3Exit the process after cleanup to avoid unstable server state.

Performance Quiz - 3 Questions

What is the main performance risk of not implementing graceful shutdown on errors in Node.js servers?

A Server will use less memory

B Server will respond faster to requests

C Server may block new requests causing slow or no responses

D Server will automatically restart without delay

DevTools: Network

How to check: Open DevTools Network panel, simulate server error, and observe if requests hang or fail quickly.

What to look for: Look for stalled or hanging requests indicating blocked server; fast error responses indicate good shutdown handling.

Practice

1. What is the main purpose of implementing a graceful shutdown in a Node.js application?

easy

A. To restart the server automatically after an error

B. To log all incoming requests for debugging

C. To increase the server's performance under load

D. To stop accepting new requests and clean up resources before exiting

Solution

1. Step 1: Understand graceful shutdown concept

   Graceful shutdown means stopping new work and cleaning up before the app exits.

2. Step 2: Identify the main goal

   The goal is to avoid abrupt termination by closing servers and resources properly.

3. Final Answer:

   To stop accepting new requests and clean up resources before exiting -> Option D

4. Quick Check:

   Graceful shutdown = stop new work + cleanup [OK]

Hint: Remember: graceful shutdown means clean exit, not restart [OK]

Common Mistakes:

• Confusing graceful shutdown with automatic restart
• Thinking it improves performance directly
• Assuming it only logs requests

2. Which of the following is the correct way to listen for an uncaught exception to trigger graceful shutdown in Node.js?

easy

A. process.on('uncaughtException', handler)

B. process.addListener('error', handler)

C. process.listen('uncaughtException', handler)

D. process.catch('uncaughtException', handler)

Solution

1. Step 1: Recall Node.js event listening syntax

   Node.js uses process.on(event, handler) to listen for events.

2. Step 2: Identify the correct event for uncaught exceptions

   The event name is 'uncaughtException', so process.on('uncaughtException', handler) is correct.

3. Final Answer:

   process.on('uncaughtException', handler) -> Option A

4. Quick Check:

   Use process.on for events like uncaughtException [OK]

Hint: Use process.on(event, handler) for error events [OK]

Common Mistakes:

• Using process.catch instead of process.on
• Using wrong event names like 'error' for uncaughtException
• Confusing listen with on

3. Consider this Node.js code snippet handling graceful shutdown:

const server = require('http').createServer();
process.on('SIGINT', () => {
  console.log('Shutdown signal received');
  server.close(() => {
    console.log('Server closed');
    process.exit(0);
  });
});
server.listen(3000, () => console.log('Server running'));

What will be the output if you press Ctrl+C in the terminal?

medium

A. Shutdown signal received\nServer running\nServer closed

B. Server running\nShutdown signal received\nServer closed

C. Server running\nServer closed\nShutdown signal received

D. Server closed\nShutdown signal received\nServer running

Solution

1. Step 1: Understand server start and signal handling order

   The server logs 'Server running' when it starts listening. On Ctrl+C, SIGINT triggers the handler.

2. Step 2: Trace the shutdown logs

   On SIGINT, it logs 'Shutdown signal received', then closes the server, then logs 'Server closed'.

3. Final Answer:

   Server running\nShutdown signal received\nServer closed -> Option B

4. Quick Check:

   Startup log first, then SIGINT logs in order [OK]

Hint: Remember: server.listen logs first, then signal handler logs [OK]

Common Mistakes:

• Mixing order of logs on startup and shutdown
• Assuming server closes before signal logs
• Ignoring asynchronous server.close callback

4. Given this code snippet for graceful shutdown, what is the main problem?

const server = require('http').createServer();
process.on('uncaughtException', (err) => {
  console.error('Error:', err);
  process.exit(1);
});
server.listen(3000);

medium

A. It listens on the wrong port

B. It does not log the error properly

C. It exits immediately without closing the server

D. It uses the wrong event name for errors

Solution

1. Step 1: Analyze error handling behavior

   The handler logs the error but calls process.exit(1) immediately.

2. Step 2: Check for graceful shutdown steps

   It does not close the server before exiting, which can cause abrupt termination.

3. Final Answer:

   It exits immediately without closing the server -> Option C

4. Quick Check:

   Graceful shutdown requires closing server before exit [OK]

Hint: Always close servers before calling process.exit [OK]

Common Mistakes:

• Exiting without cleanup
• Ignoring server.close in error handlers
• Assuming logging is enough

5. You want to implement a graceful shutdown that handles both SIGTERM and uncaughtException events, ensuring the server closes before exit. Which code snippet correctly achieves this?

hard

A. process.on('SIGTERM', () => { server.close(() => process.exit(0)); }); process.on('uncaughtException', (err) => { console.error(err); server.close(() => process.exit(1)); });

B. process.on('SIGTERM', () => { server.close(); }); process.on('uncaughtException', () => { process.exit(1); });

C. process.on('SIGTERM', () => { process.exit(0); }); process.on('uncaughtException', () => { process.exit(1); });

D. process.on('SIGTERM', () => { console.log('Terminated'); }); process.on('uncaughtException', (err) => { console.error(err); });

Solution

1. Step 1: Check handling of SIGTERM

   process.on('SIGTERM', () => { server.close(() => process.exit(0)); }); process.on('uncaughtException', (err) => { console.error(err); server.close(() => process.exit(1)); }); closes the server and then exits, which is correct for graceful shutdown.

2. Step 2: Check handling of uncaughtException

   process.on('SIGTERM', () => { server.close(() => process.exit(0)); }); process.on('uncaughtException', (err) => { console.error(err); server.close(() => process.exit(1)); }); logs the error, closes the server, then exits with error code, ensuring cleanup.

3. Final Answer:

   process.on('SIGTERM', () => { server.close(() => process.exit(0)); }); process.on('uncaughtException', (err) => { console.error(err); server.close(() => process.exit(1)); }); -> Option A

4. Quick Check:

   Close server before exit on signals and errors [OK]

Hint: Always close server before exit on signals and errors [OK]

Common Mistakes:

• Exiting immediately without closing server
• Not logging errors on uncaughtException
• Ignoring asynchronous server.close callback