WIP Have relay actor remove itself from clients #3103
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Still WIP.
It seems to me that if a relay client actor errors almost anywhere (for example when reading from the connection to the client, which happens all the time) then that
Client
never gets removed from theClients
unless someone else tries sending a message to that node.The
ConnectionId
thing is a pattern I've found useful for handling connection replacements. When the new connection gets put into theClients
list and then the old one gets shutdown, if we didn't check the connection id then the old connection would remove the new one from the list.Also I haven't tested these changes at all, just interested in getting thoughts on them
Breaking Changes
None?
Notes & open questions
Change checklist