Skip to content
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

Close connections to nodes not returned by address provider #77

Closed
akudiyar opened this issue Mar 3, 2021 · 2 comments · Fixed by #183
Closed

Close connections to nodes not returned by address provider #77

akudiyar opened this issue Mar 3, 2021 · 2 comments · Fixed by #183
Assignees
Labels
0.5sp Weight 0.5 SP bug Something isn't working

Comments

@akudiyar
Copy link
Collaborator

akudiyar commented Mar 3, 2021

Currently, the existing connections to the addresses that were not returned by the address provider during the next connection sequence, are not closed after establishing new connections, although new requests will not be dispatched to them. If such connections will not be closed by the server, they may stay alive for a long time and affect the client resources.

These "old" connections must be closed after the new ones are established if they are not already closed by a disconnect event.

@akudiyar akudiyar added bug Something isn't working 0.5sp Weight 0.5 SP labels Mar 3, 2021
@akudiyar akudiyar added this to the Q1 2021 milestone Mar 3, 2021
@akudiyar akudiyar changed the title Close connections to nodes, not returned by address provider Close connections to nodes not returned by address provider Mar 3, 2021
@vrogach2020 vrogach2020 removed this from the Q1 2021 milestone Sep 14, 2021
@vrogach2020
Copy link
Contributor

@wey1and seems to be fixed by
#167

Can we close it ?

@vrogach2020
Copy link
Contributor

@wey1and need research, please test this case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.5sp Weight 0.5 SP bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants