0 
Error: BrokenPipe: server socket closed. Please check that client side networking configurations such as Proxies, firewalls, VPN, etc. are not affecting your network connection.

DBT newbie here. Currently I am running DBT locally with following versions & settings: "dbt-core>=1.9.1" "dbt-redshift>=1.9.0"

Thread size: 4

I am trying to create two models in Redshift. First model is reading from an external table within Redshift. This table takes 80secs as a startup time irrespective of how many rows I am calling. The second table is reading from this model with some additional joins from other models.

However, I am consistently getting this error: BrokenPipe: server socket closed. Please check that client side networking configurations such as Proxies, firewalls, VPN, etc. are not affecting your network connection.

Reading online it seems like keepalives_idle is deprecated. How can I resolve this issue?

I have tried materiliazing the staging model as ephemeral and second model as table but the issue is still there.

Reading online I am cannot see any additional setting I can apply to my Redshift.

Any help/guidance?

Improve this question
Related questions
0
Assert database error on DBT model on Redshift
2
Read Redshift external table in DBT
1
redshift column encoding with dbt
Load 6 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.