1 Answer
- Newest
- Most votes
- Most comments
0
It might be you have too many partitions and thus trying to use too many connections which Redshift might not accept.
You can you the option numPartitions to control this parallelism (or just repartition the data).
Please note using JDBC on Redshift as the data grows is inefficient, the Glue connector will scale much better (you can convert your DataFrame to DynamicFrame): https://docs.aws.amazon.com/glue/latest/dg/aws-glue-programming-etl-connect-redshift-home.html#aws-glue-programming-etl-connect-redshift-write
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago