How cluster module works in Node.js - Quick Revision & Summary

Recall & Review

beginner

What is the purpose of the Node.js cluster module?

The cluster module allows Node.js to create child processes (workers) that share the same server port, enabling better use of multi-core CPUs and improving performance by handling multiple requests in parallel.

intermediate

How does the cluster module share server ports among worker processes?

Worker processes listen on the same port, and the operating system distributes incoming connections to workers using round-robin load balancing (on some platforms), allowing load balancing across CPU cores without conflicts.

intermediate

What is the role of the master process in the cluster module?

The master process manages worker processes: it creates them, listens for their exit events, and can restart workers if they crash, ensuring the application stays available.

advanced

How do worker processes communicate with the master process in the cluster module?

Workers and the master communicate using an IPC (Inter-Process Communication) channel, allowing them to send messages and coordinate tasks like graceful shutdowns or sharing state.

intermediate

What happens if a worker process crashes in a Node.js cluster setup?

The master process detects the crash via an 'exit' event and can automatically spawn a new worker to replace the crashed one, keeping the service running smoothly.

What does the Node.js cluster module primarily help with?

A Creating user interfaces

B Improving database queries

C Managing file uploads

D Utilizing multiple CPU cores to handle requests

The cluster module helps Node.js apps use multiple CPU cores by creating worker processes.

Who creates the worker processes in a Node.js cluster?

A The master process

B Each worker creates itself

C The operating system automatically

D The client browser

The master process is responsible for creating and managing worker processes.

How do workers share the same port in a cluster?

A Workers do not share ports

B The operating system distributes connections to workers

C Each worker listens on a different port

D Workers use different IP addresses

Workers listen on the shared port, and the operating system distributes incoming connections to workers.

What happens when a worker crashes in a cluster?

A The master restarts a new worker

B The whole server stops

C Nothing happens automatically

D The client reconnects automatically

The master detects the crash and can restart a new worker to maintain service.

Which communication method is used between master and workers?

A HTTP requests

B WebSockets

C IPC (Inter-Process Communication)

D File system polling

Master and workers communicate via IPC channels built into Node.js cluster.

Explain how the Node.js cluster module improves application performance on multi-core systems.

Think about how multiple workers handle requests at the same time.

Describe the lifecycle of a worker process in the Node.js cluster module.

Consider what happens from start to crash and restart.

Practice

1. What is the main purpose of the cluster module in Node.js?

easy

A. To provide a graphical user interface for Node.js apps

B. To manage database connections efficiently

C. To handle file system operations asynchronously

D. To create multiple worker processes to use all CPU cores

Solution

1. Step 1: Understand the cluster module role

   The cluster module allows Node.js to create multiple worker processes.

2. Step 2: Recognize the benefit

   These workers use all CPU cores to improve performance by handling requests in parallel.

3. Final Answer:

   To create multiple worker processes to use all CPU cores -> Option D

4. Quick Check:

   cluster module = multiple workers for CPU cores [OK]

Hint: Cluster = multiple processes for CPU cores [OK]

Common Mistakes:

• Confusing cluster with database or file system modules
• Thinking cluster manages UI or frontend
• Assuming cluster runs code in a single process

2. Which of the following is the correct way to check if the current process is the master in a cluster setup?

easy

A. if (cluster.isMaster) { ... }

B. if (cluster.isPrimary) { ... }

C. if (cluster.isWorker) { ... }

D. if (cluster.isMain) { ... }

Solution

1. Step 1: Recall the updated property name

   In recent Node.js versions, cluster.isPrimary replaces cluster.isMaster.

2. Step 2: Identify the correct syntax

   Using cluster.isPrimary correctly checks if the process is the primary (master) process.

3. Final Answer:

   if (cluster.isPrimary) { ... } -> Option B

4. Quick Check:

   Primary process check = cluster.isPrimary [OK]

Hint: Use cluster.isPrimary, not isMaster [OK]

Common Mistakes:

• Using deprecated cluster.isMaster instead of cluster.isPrimary
• Confusing isWorker with isPrimary
• Using non-existent properties like isMain

3. Consider this Node.js cluster code snippet:

const cluster = require('cluster');
const http = require('http');

if (cluster.isPrimary) {
  cluster.fork();
  cluster.fork();
} else {
  http.createServer((req, res) => {
    res.end('Worker ' + process.pid);
  }).listen(8000);
}

What will happen when you visit http://localhost:8000 multiple times?

medium

A. You will see responses from different worker process IDs

B. Only one worker will handle all requests

C. The server will crash because of multiple forks

D. You will get a syntax error on startup

Solution

1. Step 1: Understand cluster.fork creates workers

   Two workers are created, each running the HTTP server on port 8000.

2. Step 2: Recognize load balancing behavior

   Requests are distributed between workers, so responses show different process IDs.

3. Final Answer:

   You will see responses from different worker process IDs -> Option A

4. Quick Check:

   Multiple workers share port, respond with different PIDs [OK]

Hint: Multiple forks = multiple workers respond differently [OK]

Common Mistakes:

• Thinking only one worker handles all requests
• Assuming server crashes due to multiple forks
• Expecting syntax errors from this code

4. What is wrong with this cluster code snippet?

const cluster = require('cluster');
if (cluster.isPrimary) {
  cluster.fork();
} else {
  console.log('Worker running');
}

medium

A. cluster.isPrimary is deprecated, should use isMaster

B. No call to cluster.fork in the worker process

C. Missing server code inside worker

D. No error, code works fine

Solution

1. Step 1: Check cluster usage

   The primary forks one worker, which only logs a message but does not start a server.

2. Step 2: Identify missing functionality

   Without server code, the worker does not handle requests, so the cluster setup is incomplete.

3. Final Answer:

   Missing server code inside worker -> Option C

4. Quick Check:

   Worker must run server code to handle requests [OK]

Hint: Workers need server code to handle requests [OK]

Common Mistakes:

• Confusing isPrimary with deprecated isMaster
• Expecting cluster.fork in worker process
• Assuming code runs without server in worker

5. You want to create a cluster that automatically restarts a worker if it crashes. Which approach correctly implements this behavior?

hard

A. Listen to the 'exit' event on cluster and fork a new worker inside the handler

B. Use setInterval to fork new workers every second

C. Call cluster.fork() only once at startup and never again

D. Use cluster.disconnect() inside the worker to restart itself

Solution

1. Step 1: Understand worker crash handling

   The primary process can listen to the 'exit' event when a worker dies.

2. Step 2: Restart worker on exit

   Inside the 'exit' event handler, calling cluster.fork() creates a new worker to replace the crashed one.

3. Final Answer:

   Listen to the 'exit' event on cluster and fork a new worker inside the handler -> Option A

4. Quick Check:

   Restart crashed workers by handling 'exit' event [OK]

Hint: Use 'exit' event to restart workers automatically [OK]

Common Mistakes:

• Forking workers repeatedly with setInterval causes overload
• Not restarting workers after crash leads to downtime
• Using cluster.disconnect() inside worker does not restart it