-
Notifications
You must be signed in to change notification settings - Fork 14
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
vl3 healing #289
Comments
This was referenced Feb 1, 2024
This was referenced Feb 12, 2024
Closed
This was referenced Mar 19, 2024
Merged
denis-tingaikin
moved this from Under review
to Moved to next release
in Release v1.13.0
Apr 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Proposal
vl3 network doesn't have healing. We can't use original healing in this case because when one vl3 endpoint dies, a new vl3 endpoint automatically reconnects to all other vl3 NSEs when it's created.
For vl3 networks we only need to cleanup resources when vl3 endpoints die.
There are two main cases:
1. Client-side of the connection dies
In this case we have
timeout
chain element that will eventually close the connection from the dead vl3 NSE.2. Server-side of the connection dies
In this case we get the leaked connection because client doesn't close it.
Therefore, we need a client chain element that closes connections to the dead vl3 NSEs.
Solution
Create a client chain element that monitors NSEs to which it has a connection. If it gets
deleted:true
event from the registry for any of these NSEs it should automatically Close the client-side of the connections to the deleted vl3 NSE.The text was updated successfully, but these errors were encountered: