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

don't use master connection for on-run-start|end #657

Closed
drewbanin opened this issue Feb 16, 2018 · 1 comment
Closed

don't use master connection for on-run-start|end #657

drewbanin opened this issue Feb 16, 2018 · 1 comment
Assignees
Labels
bug Something isn't working redshift snowflake

Comments

@drewbanin
Copy link
Contributor

This can lead to timeout errors on Snowflake and Redshift, eg:

DatabaseException: Database Error
  server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.

The master connection is used throughout the run, so it's a little perplexing that it somehow gets disconnected. In particular, it looks like this happens when dbt calls

adapter.clear_transaction(profile)

in the ModelRunner. The line that fails is a BEGIN statement.

@drewbanin drewbanin added bug Something isn't working redshift snowflake labels Feb 16, 2018
@drewbanin drewbanin self-assigned this Feb 16, 2018
@drewbanin drewbanin added this to the Adapter Parity milestone Mar 6, 2018
@cmcarthur
Copy link
Member

fixed by #693

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

No branches or pull requests

2 participants