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

fix: simple backoff strategy after 3 subscribe failures #1238

Merged
merged 1 commit into from
Oct 4, 2024

Conversation

chaitanyaprem
Copy link
Collaborator

@chaitanyaprem chaitanyaprem commented Oct 3, 2024

Description

Fixes status-im/status-go#5679 where due to DNS failure, filter subscribe loop is going into infinite loop leading to log flooding.

  • Added a errorCount which is incremented in case of error that requires a backoff such as "no suitable peers found" . As of now the backoff is fixed and not exponential.

waku/v2/api/filter/filter.go Outdated Show resolved Hide resolved
waku/v2/utils/peer.go Show resolved Hide resolved
@chaitanyaprem chaitanyaprem merged commit 0ed94ce into master Oct 4, 2024
12 checks passed
@chaitanyaprem chaitanyaprem deleted the fix/filter-loop branch October 4, 2024 05:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Rapid log file growth and repeated Waku errors when DNS encryption is not set
2 participants