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

tag kbucket peers for better connection closing #95

Merged
merged 1 commit into from
Oct 11, 2017

Conversation

whyrusleeping
Copy link
Contributor

No description provided.

@whyrusleeping
Copy link
Contributor Author

cc @Kubuxu @Stebalien @vyzo

This should be good enough, though the failing test seems odd (but fairly certain it was there before this PR)

@Kubuxu
Copy link
Member

Kubuxu commented Oct 9, 2017

It seems like Travis has just hanged the tests. Go should timeout after 10min, ahh. Travis also does 10min so we have no idea if it was Travis or tests.

Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

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

LGTM. It would be better if we could rank peers based on their location in the bucket but that's going to take some larger changes (need an event for moving peers within buckets for one).

@Kubuxu
Copy link
Member

Kubuxu commented Oct 10, 2017

Yes, it would make sense to mark few peers per bucket with higher priority, this way might keep few in each bucket instead of loosing whole bucket.

@whyrusleeping whyrusleeping merged commit afa8222 into master Oct 11, 2017
@whyrusleeping whyrusleeping deleted the feat/conn-tagging branch October 11, 2017 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants