-
Notifications
You must be signed in to change notification settings - Fork 4.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
[BUG] Coccurency rpc operation might lead tcp connections leak. #15983
Comments
How many connections build on alert-server? Is this equal to the number of tasks running after restarting the service? How many worker-servers do you have? |
Mybe we need to further check the problem, print the connection port at the close channel, and check whether the ports in the system include closed ports.Analyze whether the closing method is called but the channel is not closed。 |
I will test and observe it at version of 3.1.9, if there is a problem too, I'll dicuss it here and then submit a pr to fix this. |
|
Good catch, this is due to the concurrent problem in NettyRemotingClient, if multiple operations belong to one host come at the same time, might create multiple channels. I submit #16021 to fix this. |
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs. |
This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future. |
Search before asking
What happened
#15954 there are detailed infomation here.
there are too many 127.0.0.1:50052 connections, and they lead tcp connection leak. i think it also has the same problem at 3.1.x, but i didn't test it.
What you expected to happen
no
How to reproduce
no
Anything else
No response
Version
3.1.x
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: