[Solved] Find the bug in this Node.js cluster code:const cluster = require('cluster'); if (cluster.isPrimary) { for (let i = 0; i | Node.js

Node.js - Cluster Module

Find the bug in this Node.js cluster code:

const cluster = require('cluster');
if (cluster.isPrimary) {
  for (let i = 0; i <= 4; i++) {
    cluster.fork();
  }
  console.log('Workers:', Object.keys(cluster.workers).length);
} else {
  console.log('Worker started');
}

ALoop runs 5 times, but only 4 CPU cores exist, causing overhead.

Bcluster.fork() must be called asynchronously.

CNo bug; code runs fine regardless of CPU cores.

DUsing '<=' causes one extra worker beyond CPU cores.

Step-by-Step Solution

Solution:

Step 1: Analyze loop condition
The loop runs from 0 to 4 inclusive, totaling 5 iterations.
Step 2: Compare with CPU cores
Forking 5 workers may exceed CPU cores, causing inefficiency.
Final Answer:
Using '<=' causes one extra worker beyond CPU cores. -> Option D
Quick Check:
Use '<' to match CPU core count [OK]

Quick Trick: Use '<' not '<=' to match CPU cores in loops [OK]

Common Mistakes:

Ignoring loop boundary off-by-one error
Assuming extra workers improve performance
Thinking cluster.fork() needs async call

Master "Cluster Module" in Node.js

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Perf

More Node.js Quizzes

Find the bug in this Node.js cluster code:

Step 1: Analyze loop condition

Step 2: Compare with CPU cores

Final Answer:

Quick Check:

Want More Practice?