Skip to content

Increase Dial retry timeout from 10s to 30s#542

Open
ambient-code[bot] wants to merge 1 commit intomainfrom
fix/increase-dial-retry-timeout
Open

Increase Dial retry timeout from 10s to 30s#542
ambient-code[bot] wants to merge 1 commit intomainfrom
fix/increase-dial-retry-timeout

Conversation

@ambient-code
Copy link
Copy Markdown
Contributor

@ambient-code ambient-code bot commented Apr 10, 2026

Summary

  • Increases server-side Dial retry maxTotalWait from 10s to 30s in controller_service.go:657
  • Aligns the server-side retry window with the client-side dial_timeout default (30s)
  • Fixes the E2E flake where exporters in CI take >10s to transition from Available to LeaseReady, causing repeated Dial rejections and eventual context cancellation

Fixes #538

Test plan

  • Verify the change compiles (go build / go vet pass — confirmed locally)
  • CI E2E tests should pass without the Dial rejection flake
  • Confirm no regression in Dial behavior for non-transient exporter statuses (Offline, HookFailed still fail immediately)

🤖 Generated with Claude Code

The server-side Dial retry window (10s) was too short for CI environments
where the exporter may take longer to transition from Available to
LeaseReady status. This caused repeated Dial rejections and eventual
context cancellation in E2E tests. Increasing to 30s aligns the
server-side retry with the client-side dial_timeout default.

Fixes #538

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@netlify
Copy link
Copy Markdown

netlify bot commented Apr 10, 2026

Deploy Preview for jumpstarter-docs failed. Why did it fail? →

Name Link
🔨 Latest commit 3faeb2d
🔍 Latest deploy log https://app.netlify.com/projects/jumpstarter-docs/deploys/69d94739ac9f4e000857c367

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.

E2E test failure: Dial rejected with Available status despite server-side retry fix

0 participants