Skip to content
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

Confusing log messages when using default connect_retries for HTTP connection #131

Closed
danielvdende opened this issue Dec 23, 2020 · 0 comments · Fixed by #132
Closed

Confusing log messages when using default connect_retries for HTTP connection #131

danielvdende opened this issue Dec 23, 2020 · 0 comments · Fixed by #132
Labels
bug Something isn't working

Comments

@danielvdende
Copy link
Contributor

Describe the bug

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.

The output of dbt --version:

installed version: 0.18.1
   latest version: 0.18.1

Up to date!

Plugins:
  - bigquery: 0.18.1
  - snowflake: 0.18.1
  - redshift: 0.18.1
  - postgres: 0.18.1
  - spark: 0.18.1.1

The operating system you're using:
Mac OS X Catalina
The output of python --version:
Python 3.7.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants