[ADAP-1022] [Feature] improve handling of disconnect/broken pipe exceptions thrown by redshift-connector

[colin-rogers-dbt]

Is this your first time submitting a feature request?

• I have read the expectations for open source contributors
• I have searched the existing issues, and I could not find an existing issue for this feature
• I am requesting a straightforward extension of existing dbt-redshift functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Based on commentary from the redshift-connector team (i.e. this and now that it surfaces better error messages we should update our connection logic to take advantage.

Specifically we should retry based on the number of configured retries all InterfaceError and BrokenPipe exceptions

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.

[yamjoepobuda]

We would like this issue to remain open. We are continuing to see intermittent SSH connectivity failures that appear to be client related (provider side). We are not experiencing these failures with other providers who are setup using identical Bastian hosts (Hightouch, Fivetran).