Skip to content
This repository has been archived by the owner on Jul 21, 2023. It is now read-only.

feat: tag kad-close peers #375

Merged
merged 1 commit into from
Oct 4, 2022
Merged

feat: tag kad-close peers #375

merged 1 commit into from
Oct 4, 2022

Conversation

achingbrain
Copy link
Member

When peers are added or removed from the kbuckets, if the kBucketSize closest peers change, update their peer store tags to ensure we don't close connections to them when the connection manager reaches it's max connections limit.

When peers are added or removed from the kbuckets, if the `kBucketSize`
closest peers change, update their peer store tags to ensure we don't
close connections to them when the connection manager reaches it's
max connections limit.
Copy link
Member

@mpetrunic mpetrunic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, @wemeetagain do you also wanna review this?

@achingbrain
Copy link
Member Author

I thinking maybe we want to tag them with keep-alive too, this will mean we try to reconnect on node startup.

@mpetrunic
Copy link
Member

I thinking maybe we want to tag them with keep-alive too, this will mean we try to reconnect on node startup.

I was contemplating the same but I feel like it's better if we tag them differently, on startup or pruning we can determine priorities. Like we could prune 'kad-close' tags before 'keep-alive' tags or something.

Or did you mean putting two tags?

@achingbrain
Copy link
Member Author

I was thinking keep-alive in addition to kad-close.

@mpetrunic mpetrunic merged commit df15a83 into master Oct 4, 2022
@mpetrunic mpetrunic deleted the feat/tag-kad-close-peers branch October 4, 2022 15:19
github-actions bot pushed a commit that referenced this pull request Oct 4, 2022
## [3.1.0](v3.0.6...v3.1.0) (2022-10-04)

### Features

* tag kad-close peers ([#375](#375)) ([df15a83](df15a83))
@github-actions
Copy link

github-actions bot commented Oct 4, 2022

🎉 This PR is included in version 3.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants