net.Server.listen's backlog option is no effect when use pm2 #1786

Activity

1. tangxinfa commented on Nov 24, 2015

   

   tangxinfa

   on Nov 24, 2015

   Author

   More actions

   This problem looks like come from node.js 's cluster module, still don't know how to resolve it.
2. Unitech commented on Nov 25, 2015

   

   Unitech

   on Nov 25, 2015

   Owner

   More actions

   What is that backlog?
3. tangxinfa commented on Nov 26, 2015

   

   tangxinfa

   on Nov 26, 2015

   Author

   More actions

   There is a two example, i set backlog to 64:

   Without cluster:

   var http       = require('http');
   
   http.createServer(function(req, res) {
       res.writeHead(200);
       res.end("hello world\n");
   }).listen(3000, "0.0.0.0", 64);
   

   ss -ltn | grep 3000 output:

   LISTEN     0      64           *:3000                     *:*                  
   

   With cluster

   var cluster    = require('cluster'),
       http       = require('http');
   
   
   if (cluster.isMaster) {
       cluster.fork();
   } else {
       http.createServer(function(req, res) {
           res.writeHead(200);
           res.end("hello world\n");
       }).listen(3000, "0.0.0.0", 64);
   }
   

   ss -ltn | grep 3000 output:

   LISTEN     0      511          *:3000                     *:*                  
   

   The backlog take effect is 511 not 64, this means node cluster module NOT take care of the backlog option when we call listen: server.listen(port[, hostname][, backlog][, callback])
4. tangxinfa commented on Nov 28, 2015

   

   tangxinfa

   on Nov 28, 2015

   Author

   More actions

   Already pulled a request to node: cluster, net: backlog need pass to listen #4056
5. Unitech

   closed this as completedon Jan 29, 2017
6. eladnava commented on Nov 30, 2021

   

   eladnava

   on Nov 30, 2021

   Last edited by eladnava

   More actions

   Another PR (more recent), which is also now unfortunately closed due to lack of activity: nodejs/node#33827
7. eladnava commented on Feb 25, 2022

   

   eladnava

   on Feb 25, 2022

   More actions

   This is now fixed in PR nodejs/node#41623 and published in Node 17.6.0!