Node.js 中的集群不起作用。只有一名工人始终在响应

我正在 Node.js 中练习集群，我有一个两核 CPU。我创建了两个worker，每个worker 运行一个简单的http 服务器。服务器响应回调将阻塞 5 秒，以便向其他工作人员发出下一个请求。为了验证工作人员是否并行工作，我在 Firefox 中打开了多个选项卡并刷新了每个选项卡。问题总是（99%）只有一名工作人员响应通过刷新选项卡发出的请求。一名工作人员只处理一个请求，所有其他请求都会被阻止，直到该工作人员完成为止。我的代码在这里 代码：

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



if (cluster.isMaster) {
    var cpus = require('os').cpus().length;
    console.log('No of cpus:' + cpus);
    console.log(require('os').cpus());

    for (var i = 0; i < cpus; i++) {
        cluster.fork();
    }

    cluster.on('fork', function(worker) {
        console.log('worker:' + worker.id + " is forked");
    });
    cluster.on('online', function(worker) {
        console.log('worker:' + worker.id + " is online");
    });
    cluster.on('listening', function(worker) {
        console.log('worker:' + worker.id + " is listening");
    });
    cluster.on('disconnect', function(worker) {
        console.log('worker:' + worker.id + " is disconnected");
    });
    cluster.on('exit', function(worker) {
        console.log('worker:' + worker.id + " is dead");
    });

} else {
    http.createServer(function(req, res) {

        console.log('worker:' + cluster.worker.id + " going to send response ");
        res.writeHead(200);
        res.end("hello world. worker: " + cluster.worker.id);
        var stop = new Date().getTime();
        while (new Date().getTime() < stop + 5000) {;
        }
    }).listen(8000);
}

OUTPUT:

20 Aug 00:36:11 - [nodemon] restarting due to changes...
20 Aug 00:36:12 - [nodemon] starting `node cluster.js`
No of cpus:2
[ { model: 'Intel(R) Core(TM)2 Duo CPU     E4500  @ 2.20GHz',
    speed: 2200,
    times: { user: 2264671, nice: 0, sys: 698343, idle: 5965109, irq: 98812 } },
  { model: 'Intel(R) Core(TM)2 Duo CPU     E4500  @ 2.20GHz',
    speed: 2200,
    times: { user: 2466000, nice: 0, sys: 502562, idle: 5959203, irq: 4609 } } ]
worker:1 is forked
worker:2 is forked
worker:2 is online
worker:1 is online
worker:2 is listening
worker:1 is listening
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response
worker:1 going to send response

我注意到一件事。如果我强制重新加载（ctrl+f5）选项卡，那么两个工作人员都会相继响应。 输出：

worker:1 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response
worker:1 going to send response
worker:2 going to send response

我很困惑正常刷新（f5）和强制重新加载（ctrl + f5）这里发生了什么。帮我弄清楚...！

从表面上看，TIL 节点集群似乎并没有做到它所说的那样（至少对我来说）。

我的情况与您相同，当我从浏览器同步生成它们时，观察到相同的工作进程总是收到请求。我的一位同事使用 fiddler 一次重播约 20 个请求。当所有这些请求非常快地到达服务器时，比集群管理器将它们传递给工作人员的速度更快（我猜测），那么您将看到其他工作人员被请求调用。

看起来，一旦经理将请求交给工作人员，它就不会知道/关心工作人员的阻塞。它只知道管道中只有一个请求，并且不需要将该请求提供给第一个工作人员以外的任何人，因为据经理所知，他是可用的。