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: add peer addresses on expiry if peer is discovered again #1128

Merged
merged 2 commits into from
Jun 18, 2024

Conversation

chaitanyaprem
Copy link
Collaborator

Description

While testing status-im/status-go#5350 after enabling peerExchangeClient, had noticed a good number of peer connection failures happen because of peer addresses expiring.
If a peer is discovered dynamically, its address TTL i set to default value which is 1 hour.
Eventhough the peer is discovered again later, only the ENR is updated in case of a change. This results in addresses being expired and hence failing to connect to these peers with error "no addresses".

ERROR[06-14|15:41:07.989|github.com/waku-org/go-waku/waku/v2/protocol/filter/client.go:405] Failed to subscribe pubSubTopic=/waku/2/rs/16/32 contentTopics=[/waku/1/0x7135123e/rfc26] error="failed to dial: failed to dial 16Uiu2HAkuanZeK281yniUVD9pUMWoBe2MjSknjy5gLB5LuhJj1Bk: no addresses"

Changes

  • Whenever AdddiscoveredPeer is invoked, check if addresses have expired and add them again.

@status-im-auto
Copy link

status-im-auto commented Jun 17, 2024

Jenkins Builds

Commit #️⃣ Finished (UTC) Duration Platform Result
✔️ f283821 #1 2024-06-17 07:27:38 ~1 min nix-flake 📄log
✔️ d530c6f #2 2024-06-17 08:55:27 ~1 min nix-flake 📄log

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.

3 participants