-
-
Notifications
You must be signed in to change notification settings - Fork 34.4k
cluster: fix port reuse between cluster #60141
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #60141 +/- ##
==========================================
+ Coverage 88.45% 88.52% +0.06%
==========================================
Files 703 703
Lines 207546 207821 +275
Branches 40016 40014 -2
==========================================
+ Hits 183595 183977 +382
+ Misses 15956 15857 -99
+ Partials 7995 7987 -8
🚀 New features to boost your workflow:
|
|
@islandryu - Thank you for proposing this change, the underlying issue is causing trouble for us with TCP, UDP, and HTTP servers: #60086. Any chance of getting this merged anytime in the near future? |
|
We’ll need to get this reviewed before it can move forward. @nodejs/cluster |
mcollina
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
|
Landed in 903f647 |
Fixes: #60086
If the
message.indexpassed toqueryServerbecomes out of sync due to errors or other issues, it may prevent a cluster from reusing a port that was acquired by another cluster.To address this, I modified the code so that the handle key no longer includes the index (except when the port number is 0), and only the latest handle corresponding to a successfully acquired port is stored.