-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Add aiohttp.client_exceptions.ClientConnectorError
to be a retryable error in databricks provider
#43080
Comments
+1 to making |
+1 from my side as well |
By the way we observe some problems with |
Thinking about this, I think, we can let users pass their own As of now, we only take
|
Happy to share the message:
If there is a possibility to customize the retryable error this can be a solution for me. I could imagine that some of the exception types can be dependent on the cloud provider where Databricks is running on... |
However I think a timeout should be retryable per default as this is typically something which will be fixed a little bit later... |
@lucafurrer , I will create a separate issue and take it up later today. If you can create a new issue before that, please mention me |
Description
When there are SSL handshake issues(And usually intermittent), All deferrable Databricks operators fail in deferrable mode without retrying as
aiohttp.client_exceptions.ClientConnectorError
is not a retryable error.As of now, we only consider
aiohttp.ClientResponseError
to be retryable. I would like to makeaiohttp.client_exceptions.ClientConnectorError
error to be retryable.Use case/motivation
When SSL handshake takes longer(usually 60 seconds by default), it fails with the below error:
And, that's intermittent. Making this retryable will help
Related issues
NA
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: