Connector failing to start after making the SSL changes to connect-distributed.properties

Hi,

I am having a cluster with 3 brokers and zookeepers nodes, 1 schema registry, 1 kafka connect, 1 control center, 1 ksql and 1 rest-proxy node each.

I’ve enabled SSL encryption on brokers, zookeepers and control center. Now when I did the SSL specific changes on my connector node’s connect-distributed.properties file, my connector node gets started at 1st and then fails with the timeout and gives the following error. I am hereby attaching the connect-distributed.properties file. Any suggestions will be highly appreciated.

[2021-04-15 08:11:27,033] INFO Kafka version: 5.5.0-ce (org.apache.kafka.common.utils.AppInfoParser)
[2021-04-15 08:11:27,033] INFO Kafka commitId: dad78e2df6b714e3 (org.apache.kafka.common.utils.AppInfoParser)
[2021-04-15 08:11:27,033] INFO Kafka startTimeMs: 1618474287033 (org.apache.kafka.common.utils.AppInfoParser)
[2021-04-15 08:11:57,070] INFO [AdminClient clientId=adminclient-1] Metadata update failed (org.apache.kafka.clients.admin.internals.AdminMetadataManager)
org.apache.kafka.common.errors.TimeoutException: Call(callName=fetchMetadata, deadlineMs=1618474317068) timed out at 1618474317069 after 1 attempt(s)
Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting to send the call.
[2021-04-15 08:12:27,069] INFO [AdminClient clientId=adminclient-1] Metadata update failed (org.apache.kafka.clients.admin.internals.AdminMetadataManager)
org.apache.kafka.common.errors.TimeoutException: Call(callName=fetchMetadata, deadlineMs=1618474347069) timed out at 9223372036854775807 after 1 attempt(s)
Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting to send the call.
[2021-04-15 08:12:27,075] ERROR Stopping due to error (org.apache.kafka.connect.cli.ConnectDistributed)
org.apache.kafka.connect.errors.ConnectException: Failed to connect to and describe Kafka cluster. Check worker's broker connection and security properties.
        at org.apache.kafka.connect.util.ConnectUtils.lookupKafkaClusterId(ConnectUtils.java:64)
        at org.apache.kafka.connect.util.ConnectUtils.lookupKafkaClusterId(ConnectUtils.java:45)
        at org.apache.kafka.connect.cli.ConnectDistributed.startConnect(ConnectDistributed.java:95)
        at org.apache.kafka.connect.cli.ConnectDistributed.main(ConnectDistributed.java:78)
Caused by: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Call(callName=listNodes, deadlineMs=1618474347066) timed out at 1618474347067 after 1 attempt(s)
        at org.apache.kafka.common.internals.KafkaFutureImpl.wrapAndThrow(KafkaFutureImpl.java:45)
        at org.apache.kafka.common.internals.KafkaFutureImpl.access$000(KafkaFutureImpl.java:32)
        at org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:89)
        at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:260)
        at org.apache.kafka.connect.util.ConnectUtils.lookupKafkaClusterId(ConnectUtils.java:58)
        ... 3 more
Caused by: org.apache.kafka.common.errors.TimeoutException: Call(callName=listNodes, deadlineMs=1618474347066) timed out at 1618474347067 after 1 attempt(s)
Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment.

After restarting the node next time the connector gets started. But its not stable since it does fail intermittently. I am not sure if its due to some config I am missing.

Hi,

Sorry to hear about the issue. Nothing jumps out to me from looking at the log files, other than with a timeout the workers can’t connect to the broker.

The only thing I can suggest at this point is to review your broker SSL settings and maybe confirm the connect SSL settings.

HTH,
Bill