Fixing idle issue and improving debug logging #648
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hopefully resolves #647
Description
Customers with high concurrency on SQL Warehouses have been hitting an issue where they see 'Remote disconnected' as the error. It appears somewhere in the stack, connections that have been idle for 180+s hit this issue when we attempt to reuse them. This PR has the following:
Checklist
I should probably add tests for the logging, but I will hold that for when I bring this code into 2.0.0 branch (to reduce the significant pain that will already be).
CHANGELOG.md
and added information about my change to the "dbt-databricks next" section.