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

[p2p] Limit inv syncs with new peers #4734

Closed
jcnelson opened this issue Apr 30, 2024 · 1 comment
Closed

[p2p] Limit inv syncs with new peers #4734

jcnelson opened this issue Apr 30, 2024 · 1 comment
Assignees
Labels
3.0-must 3.0 bug Unwanted or unintended property causing functional harm locked

Comments

@jcnelson
Copy link
Member

It's getting expensive to sync a peer inventory from scratch, and it's an increasingly fragile process (especially with stackerdb sync). The inv state for a peer should either be kept around after disconnect (so we don't have to re-sync it), or we should avoid doing full inv syncs in the first place.

Also, a stackerdb disconnect should not result in a whole-sale peer disconnect.

@jcnelson jcnelson added the bug Unwanted or unintended property causing functional harm label Apr 30, 2024
@jcnelson jcnelson self-assigned this Apr 30, 2024
@jcnelson jcnelson mentioned this issue May 3, 2024
@saralab saralab closed this as completed May 9, 2024
@blockstack-devops
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Oct 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
3.0-must 3.0 bug Unwanted or unintended property causing functional harm locked
Projects
Archived in project
Development

No branches or pull requests

3 participants