How do you implement graceful shutdown?

Question

Accepted Answer

**Graceful shutdown** means stopping a server cleanly when it receives a termination signal — finishing in-flight requests, closing connections (DB, etc.), and releasing resources — instead of abruptly killing it and dropping active work. It's essential for zero-downtime deploys and reliability.

## Why abrupt shutdown is a problem

```text
Without graceful shutdown, when the process is killed (deploy, scale-down, crash):
  ✗ In-flight requests are dropped → users get errors
  ✗ DB transactions left incomplete
  ✗ Connections not closed cleanly → leaks/locks
```

During deploys and autoscaling, processes are stopped constantly — doing it cleanly is what makes deployments seamless.

## Implementing it

```js
import http from "http";
const server = http.createServer(app);
server.listen(3000);

async function shutdown(signal) {
  console.log(`${signal} received — shutting down gracefully`);

// 1. Stop accepting NEW connections; finish existing ones
  server.close(async () => {
    // 2. This callback runs once all active requests have completed
    await db.end();            // close database pool
    await redis.quit();        // close other connections
    console.log("clean shutdown complete");
    process.exit(0);           // exit successfully
  });

// 3. Safety net: force-exit if cleanup hangs too long
  setTimeout(() => {
    console.error("forced shutdown — cleanup timed out");
    process.exit(1);
  }, 10_000).unref();
}

// Listen for termination signals
process.on("SIGTERM", () => shutdown("SIGTERM")); // sent by orchestrators (k8s, Docker)
process.on("SIGINT", () => shutdown("SIGINT"));   // Ctrl+C in dev
```

The sequence: catch the signal → `server.close()` (stop new connections, drain existing) → close DB/Redis/other resources → exit. A **timeout fallback** force-exits if something hangs, so a stuck connection can't block shutdown forever.

## The signals

```text
SIGTERM → the standard "please terminate" signal from orchestrators on deploy/scale-down
SIGINT  → Ctrl+C (development)
SIGKILL → cannot be caught (force kill) — graceful shutdown can't help here
```

## In containerized environments

```text
Kubernetes/Docker send SIGTERM, wait a grace period (e.g. 30s), THEN SIGKILL.
Your app must finish within that window → keep the shutdown timeout shorter.
Readiness probes should mark the pod unready so the load balancer stops sending traffic.
```

## Why it matters

Graceful shutdown is what enables **zero-downtime deployments** and reliable operation in modern (especially containerized/orchestrated) environments, where processes are routinely stopped and restarted.

Without it, every deploy or scale-down drops active requests and risks data inconsistency.

Implementing the catch-signal → stop-accepting → drain → close-resources → exit sequence (with a timeout safety net) is a hallmark of production-ready Node services and a frequently-overlooked but important operational concern.