-
Notifications
You must be signed in to change notification settings - Fork 45
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
feat: Sharded peer management - Relay #764
Conversation
Jenkins BuildsClick to see older builds (54)
|
… adds them to store
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.
The logic is good.
In practice it might have problems if there's a lot of node churn.
Until we have something more sophisticated this works.
P.S. can't read Go very well.
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.
nice PR. Looking fwd to see it in action.
I added some minor comments / nitpick (like reducing verbosity of some logs), but overall it looks great
Co-authored-by: richΛrd <info@richardramos.me>
* chore: add config to limit peerstore capacity * fix: expire peer addresses discovered dynamically,remove them from peerStore after expiry
Description
Ensure healthy relay peer connections for pubSub topics or shards subscribed to by the node.
Refer to issue #727 for overall scope.
Changes
Tests