Skip to content

Reconnect feeder after request timeout - #4225

Closed
FilipLaurentiu wants to merge 1 commit into
NethermindEth:mainfrom
FilipLaurentiu:filip/create_new_connection_after_timeout
Closed

FilipLaurentiu wants to merge 1 commit into
NethermindEth:mainfrom
FilipLaurentiu:filip/create_new_connection_after_timeout

Conversation

@FilipLaurentiu

Copy link
Copy Markdown

Summary

  • Close idle HTTP connections when a feeder request times out, ensuring a retry establishes a fresh connection after WAN failover.
  • Add a regression test that expires the configured gateway timeout and verifies the retry uses a different connection.

Validation

  • go test ./clients/feeder -run TestClientRetryBehavior -count=1
  • go test ./clients/feeder -count=1

Close idle HTTP connections before retrying timed-out feeder requests so WAN failover can use the new route. Add coverage for a retry after the configured gateway timeout expires.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@FilipLaurentiu

Copy link
Copy Markdown
Author

This changes are needed in a multi-WAN setup. If the main ISP fail, the second should pick up, so the old connections should be dropped and not tried again

@brbrr

brbrr commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

Thanks for the PR! While reviewing your PR, I found another way to address the issue, so I've opened #4227, and I'll close this one if you don't mind.

@brbrr brbrr closed this Oct 27, 2026
@FilipLaurentiu

Copy link
Copy Markdown
Author

Thanks for the PR! While reviewing your PR, I found another way to address the issue, so I've opened #4227, and I'll close this one if you don't mind.

Definitely ! Thank you for fixing it

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.

2 participants