Getting broker disconnected errors in Confluent redshift sink connector

Question

Hi,
I am trying to work Redshift sink connector working with MSK Connect. I am always getting timed out errors/broker disconnects even though there is no problem with network configuration(confirmed that connector is able to create its internal topics during creation part, but then it fails by giving timed out exception).
Following is the configuration i am using:

```
connector.class=io.confluent.connect.aws.redshift.RedshiftSinkConnector
aws.redshift.port=5439
confluent.topic.bootstrap.servers=****
tasks.max=2
topics=****
aws.redshift.password=****
aws.redshift.database=****
delete.enabled=true
confluent.topic.replication.factor=1
aws.redshift.user=****
auto.create=true
pk.mode=true
```
What is the missing/wrong configuration or issue here?

Answer

Hi there,

Timed out errors or broker disconnects while creating a connector in MSK Connect can be due to various reasons. In order to troubleshoot this further, we require details that are non-public information. Please open a support case with AWS using the following link:

https://console.aws.amazon.com/support/home#/case/create

Getting broker disconnected errors in Confluent redshift sink connector

Relevant content