Skip to content
This repository has been archived by the owner on May 2, 2023. It is now read-only.

Facing issue on multiple kafka connect for debezium mssql connector and zeebe using confluent operator #928

Open
Gopiprasanth3070 opened this issue Feb 15, 2023 · 0 comments

Comments

@Gopiprasanth3070
Copy link

I deployed the kafka connect for zeebe using confluent operator to the minikube cluster it is working. If I deploy the second kafka connect for debezium mssql connector using confluent operator it is failing.

this is the error i am getting.

+++
[main] WARN org.apache.kafka.clients.ClientUtils - Couldn't resolve server PLAINTEXT://debezium-cp-kafka-headless:9092 from bootstrap.servers as DNS resolution failed for debezium-cp-kafka-headless
[main] ERROR io.confluent.admin.utils.cli.KafkaReadyCommand - Error while running kafka-ready.
org.apache.kafka.common.KafkaException: Failed to create new KafkaAdminClient
at org.apache.kafka.clients.admin.KafkaAdminClient.createInternal(KafkaAdminClient.java:407)
at org.apache.kafka.clients.admin.AdminClient.create(AdminClient.java:65)
at io.confluent.admin.utils.ClusterStatus.isKafkaReady(ClusterStatus.java:138)
at io.confluent.admin.utils.cli.KafkaReadyCommand.main(KafkaReadyCommand.java:150)
Caused by: org.apache.kafka.common.config.ConfigException: No resolvable bootstrap urls given in bootstrap.servers
at org.apache.kafka.clients.ClientUtils.parseAndValidateAddresses(ClientUtils.java:88)
at org.apache.kafka.clients.ClientUtils.parseAndValidateAddresses(ClientUtils.java:47)
at org.apache.kafka.clients.admin.KafkaAdminClient.createInternal(KafkaAdminClient.java:367)
... 3 more
+++

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant