Skip to content

Retry on Faraday::ConnectionFailed (DNS/TCP transient errors) v0.5.3#42

Merged
marcosgz merged 2 commits into
mainfrom
retry-connection-failed
May 20, 2026
Merged

Retry on Faraday::ConnectionFailed (DNS/TCP transient errors) v0.5.3#42
marcosgz merged 2 commits into
mainfrom
retry-connection-failed

Conversation

@marcosgz

@marcosgz marcosgz commented May 19, 2026

Copy link
Copy Markdown
Owner

Summary

Faraday::ConnectionFailed (DNS resolution failure, TCP connection refused) was crashing import jobs instead of retrying. This adds it to the existing transient-error rescue block alongside 502/503/504/429, so it retries with the same exponential backoff (2s → 4s → raises).

Example error that is now retried:

Faraday::ConnectionFailed: Failed to open TCP connection to pipeline.oss.locallabs.com:443 (getaddrinfo: Try again)

Bumps version to 0.5.3, updates all Gemfile locks.

Test plan

  • STUB_STACK=elasticsearch-7.17.0 BUNDLE_GEMFILE=gemfiles/Gemfile.elasticsearch-7.x bundle exec rspec spec/esse/import/bulk_spec.rb — 16 examples, 0 failures

marcosgz added 2 commits May 19, 2026 17:45
Adds Faraday::ConnectionFailed to the transient-error retry block so
DNS resolution failures and TCP connection errors are retried with the
same exponential backoff as 502/503/504, instead of crashing the import.

Bumps version to 0.5.3.
@marcosgz
marcosgz merged commit 3ba27c2 into main May 20, 2026
41 of 42 checks passed
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.

1 participant