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: Increase pubsub message seen TTL from 120s to two epochs #14030

Closed
wants to merge 2 commits into from

Conversation

prestonvanloon
Copy link
Member

@prestonvanloon prestonvanloon commented May 21, 2024

What type of PR is this?

Bug fix

What does this PR do? Why is it needed?

Since attestations are valid for two epochs, it is more appropriate to maintain a history of these
seen messages for two epochs so that Prysm is not redundantly sending valid attestations through the
network.

Which issues(s) does this PR fix?

Other notes for review

This matches Lighthouse's configuration

This PR also changes the log level of expired attestations to debug since it was occuring so often
during my testing and some users have reported it.

Default: https://github.com/libp2p/go-libp2p-pubsub/blob/dbd1c9eadedc402fa40ba3e45296594d7e828110/pubsub.go#L32

@prestonvanloon prestonvanloon requested a review from a team as a code owner May 21, 2024 20:12
@prestonvanloon prestonvanloon added the Ready For Review A pull request ready for code review label May 21, 2024
Copy link
Contributor

@saolyn saolyn left a comment

Choose a reason for hiding this comment

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

LGTM, but best to wait for @nisdas feedback

Copy link
Member

@nisdas nisdas left a comment

Choose a reason for hiding this comment

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

@nisdas
Copy link
Member

nisdas commented May 22, 2024

The log issue has been fixed in an earlier PR:
#13858

However, we have not had a release for it

@prestonvanloon
Copy link
Member Author

@nisdas that constant is never used.

The log issue is still present. I am seeing it constantly when running this very PR from commit 786ee92

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ready For Review A pull request ready for code review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants