Suggestion with cluster module when use "maxConnection" in its worker process #54882
Labels
cluster
Issues and PRs related to the cluster subsystem.
feature request
Issues that request new features to be added to Node.js.
What is the problem this feature will solve?
When the node service is under a very high load, multiple connections are processed at the same time in one worker ( we use the cluster module currently in our project ). We set the "maxConnections" to limit the connections of the worker. But we found that if a new request reach the limit of the "maxConnections", the request will retry on other workers. I think can we have an option, if a new request reach the limit, we can just drop the request instead of retrying the request on other workers ? Because as the system is under a very high load, the other workers may also be very busy at this moment. Here is a example on "v22.7.0".
What is the feature you are proposing to solve the problem?
For example, add An option "--maxconnections-drop-request" to the node "Command-line options" while on start up.
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: