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

[Flight] JDBC driver: cache failed connection attempts and make connect timeout adjustible #494

Open
lidavidm opened this issue Jan 9, 2025 · 0 comments · May be fixed by #495
Open

[Flight] JDBC driver: cache failed connection attempts and make connect timeout adjustible #494

lidavidm opened this issue Jan 9, 2025 · 0 comments · May be fixed by #495
Assignees
Labels
Type: enhancement New feature or request

Comments

@lidavidm
Copy link
Member

lidavidm commented Jan 9, 2025

Describe the enhancement requested

  • The default connect timeout is 30 seconds. This is rather painful when the server returns an address that isn't reachable. (Example: the server is deployed on a Kubernetes cluster that is being accessed via proxy/port-forwarding, and the server has a separated data plane/control plane.)
  • We hit this timeout on every query. As a stepping stone to full caching of clients ([Java][Flight] Add caching of FlightClients to JDBC #157), we can cache failures and avoid trying those locations first on subsequent queries (we can still try them last in case other locations fail)
@lidavidm lidavidm added the Type: enhancement New feature or request label Jan 9, 2025
lidavidm added a commit to lidavidm/arrow-java that referenced this issue Jan 9, 2025
- Expose gRPC for the client builder
- Cache failed locations and try them last
- Allow configuring the connect timeout

Fixes apache#494.
@lidavidm lidavidm self-assigned this Jan 9, 2025
lidavidm added a commit to lidavidm/arrow-java that referenced this issue Jan 9, 2025
- Expose gRPC for the client builder
- Cache failed locations and try them last
- Allow configuring the connect timeout

Fixes apache#494.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant