You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
Describe the enhancement requested
The text was updated successfully, but these errors were encountered: