Hi @MDB Admin
The error you're encountering:
[Databricks][DatabricksJDBCDriver] Communication link failure.
Failed to connect to server. Reason: HTTP retry after response received with no Retry-After header.
Error: HTTP Response code: 503, Error message: TEMPORARILY_UNAVAILABLE
...typically indicates a transient availability issue with the Serverless SQL Warehouse in Azure Databricks.
Here's what it means and what you can do:
- The HTTP 503 error suggests that the target service (Databricks SQL Warehouse) was temporarily unavailable at the time of the connection attempt.
- This may be due to high load, auto-scaling delays, or internal transient faults within the Databricks backend.
- The absence of a
Retry-After
header means the client isn't given guidance on when to retry, which is why the connector fails without auto-recovery.
Recommended Steps:
- Retry Logic: Make sure your SAAS connector or JDBC client includes robust retry logic with exponential backoff for transient errors like these.
- Check SQL Warehouse Status: Confirm that the target SQL Warehouse is running and healthy. If it's set to auto-stop, it may take some time to start up under load.
- Review Capacity Settings: If you're seeing this issue frequently:
- Consider increasing the min/max cluster size for your SQL Warehouse.
- Review your concurrency limits and query volume.
- Monitor via Databricks: Use the SQL Warehouse event logs to see recent startup attempts, scaling actions, or failed connection events for more insight.
Contact Databricks Support with request IDs, timestamps, and SQL Warehouse names to investigate backend service availability if it doesn’t resolve.
I hope this information helps. Please do let us know if you have any further queries.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.