-
Notifications
You must be signed in to change notification settings - Fork 120
Closed
Description
we use dbt-databricks (which uses databricks-sql-connector)
databricks-sql-connector==2.6.2 (but seems to be relevant to current version of the library.
dbt-databricks==1.5.4
And we experience lots of errors if our databricks cluster is under heavy load. And restarts cause more load...
Relevant traceback:
[2023-09-07, 11:04:25 UTC] {subprocess.py:93} INFO - �[0m11:04:25 Databricks adapter: <class 'databricks.sql.exc.RequestError'>: Error during request to server
[2023-09-07, 11:04:25 UTC] {subprocess.py:93} INFO - �[0m11:04:25 Databricks adapter: attempt: 1/30
[2023-09-07, 11:04:25 UTC] {subprocess.py:93} INFO - �[0m11:04:25 Databricks adapter: bounded-retry-delay: None
[2023-09-07, 11:04:25 UTC] {subprocess.py:93} INFO - �[0m11:04:25 Databricks adapter: elapsed-seconds: 6.919969797134399/900.0
[2023-09-07, 11:04:25 UTC] {subprocess.py:93} INFO - �[0m11:04:25 Databricks adapter: error-message:
[2023-09-07, 11:04:25 UTC] {subprocess.py:93} INFO - �[0m11:04:25 Databricks adapter: http-code: 502
[2023-09-07, 11:04:25 UTC] {subprocess.py:93} INFO - �[0m11:04:25 Databricks adapter: method: GetOperationStatus
[2023-09-07, 11:04:25 UTC] {subprocess.py:93} INFO - �[0m11:04:25 Databricks adapter: no-retry-reason: non-retryable error
[2023-09-07, 11:04:25 UTC] {subprocess.py:93} INFO - �[0m11:04:25 Databricks adapter: original-exception:
[2023-09-07, 11:04:25 UTC] {subprocess.py:93} INFO - �[0m11:04:25 Databricks adapter: query-id: b'\xac\x18\xa1\xe2\x1a\x03@S\xbf\x1a\xca\x9ad(W\x8e'
[2023-09-07, 11:04:25 UTC] {subprocess.py:93} INFO - �[0m11:04:25 Databricks adapter: session-id: None
azorej
Metadata
Metadata
Assignees
Labels
No labels