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
With a default of 0 connect_retries, confusing log messages show up. (see example below)
Running with dbt=0.18.1
Found 5 models, 12 tests, 0 snapshots, 0 analyses, 158 macros, 0 operations, 0 seed files, 3 sources
Warning: TEMPORARILY_UNAVAILABLE: Cluster <my-cluster-name> is temporarily unavailable. The current cluster state is Terminated. Please retry your request after 30 seconds.
Retrying in 10 seconds (0 of 0)
Encountered an error:
Runtime Error
Runtime Error
TEMPORARILY_UNAVAILABLE: Cluster <my-cluster-name> is temporarily unavailable. The current cluster state is Terminated. Please retry your request after 30 seconds.
We encountered this while working with Databricks, where we had a cluster that had not been started yet.
The logs suggest that a retry is going to be carried out, but it isn't (because the retry count defaults to 0). Also, a sleep is carried out, even if no retries are to happen.
Expected behavior
If connect_retries is set to 0, the logs should not state that retries are going to happen. Also the sleep after this log statement is unnecessary.
Screenshots and log output
Running with dbt=0.18.1
Found 5 models, 12 tests, 0 snapshots, 0 analyses, 158 macros, 0 operations, 0 seed files, 3 sources
Warning: TEMPORARILY_UNAVAILABLE: Cluster <my-cluster-name> is temporarily unavailable. The current cluster state is Terminated. Please retry your request after 30 seconds.
Retrying in 10 seconds (0 of 0)
Encountered an error:
Runtime Error
Runtime Error
TEMPORARILY_UNAVAILABLE: Cluster <my-cluster-name> is temporarily unavailable. The current cluster state is Terminated. Please retry your request after 30 seconds.
Describe the bug
With a default of 0 connect_retries, confusing log messages show up. (see example below)
We encountered this while working with Databricks, where we had a cluster that had not been started yet.
The logs suggest that a retry is going to be carried out, but it isn't (because the retry count defaults to 0). Also, a sleep is carried out, even if no retries are to happen.
Expected behavior
If
connect_retries
is set to 0, the logs should not state that retries are going to happen. Also the sleep after this log statement is unnecessary.Screenshots and log output
The output of
dbt --version
:The operating system you're using:
Mac OS X Catalina
The output of
python --version
:Python 3.7.9
The text was updated successfully, but these errors were encountered: