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

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

Open
3 tasks done
colin-rogers-dbt opened this issue Nov 9, 2023 · 3 comments · May be fixed by #895
Open
3 tasks done
Labels
enhancement New feature or request

Comments

@colin-rogers-dbt
Copy link
Contributor

colin-rogers-dbt commented Nov 9, 2023

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

@colin-rogers-dbt colin-rogers-dbt added enhancement New feature or request triage labels Nov 9, 2023
@github-actions github-actions bot changed the title [Feature] improve handling of disconnect/broken pipe exceptions thrown by redshift-connector [ADAP-1022] [Feature] improve handling of disconnect/broken pipe exceptions thrown by redshift-connector Nov 9, 2023
Copy link
Contributor

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 github-actions bot added the Stale label Jun 17, 2024
Copy link
Contributor

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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 25, 2024
@yamjoepobuda
Copy link

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).

@colin-rogers-dbt colin-rogers-dbt linked a pull request Aug 6, 2024 that will close this issue
4 tasks
@github-actions github-actions bot removed the Stale label Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants