-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
net.Server.listen's backlog option is no effect when use pm2 #1786
Comments
This problem looks like come from node.js 's cluster module, still don't know how to resolve it. |
What is that backlog? |
There is a two example, i set backlog to 64: Without cluster:
ss -ltn | grep 3000 output:
With cluster
ss -ltn | grep 3000 output:
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]) |
Already pulled a request to node: cluster, net: backlog need pass to listen #4056 |
Another PR (more recent), which is also now unfortunately closed due to lack of activity: nodejs/node#33827 |
This is now fixed in PR nodejs/node#41623 and published in Node |
My server's backlog set to 4096 when i call net.Server.listen
When start with pm2, backlog is 511(default value):
If use node, backlog is 4096:
My server's node version: v0.12.7, pm2 version: 0.14.3
The text was updated successfully, but these errors were encountered: