0

I'm using Confluent Platform 3.3 as a Kafka connector , while starting the connector using the below command,

./bin/connect-standalone ./etc/schema-registry/connect-avro-standalone.properties ./etc/kafka-connect-jdbc/connect-jdbc-source.properties

getting the below error 

ERROR Server died unexpectedly:  (io.confluent.kafka.schemaregistry.rest.SchemaRegistryMain:52)
org.apache.kafka.common.errors.TimeoutException: Timeout expired while fetching topic metadata
[2017-10-30 13:49:56,178] ERROR Failed to send HTTP request to endpoint: http://localhost:8081/subjects/jdbc-source-accounts-value/versions 
(io.confluent.kafka.schemaregistry.client.rest.RestService:156)

The Zookeeper is running in kafka client 2181 port, and I tried to start schema by the below command

 ./bin/schema-registry-start ./etc/schema-registry/schema-registry.properties &

But it didn't show any error messages but the port 8081 didn't up.Please help me to sort this out.

OneCricketeer
  • 179,855
  • 19
  • 132
  • 245
Raju
  • 448
  • 1
  • 9
  • 24

3 Answers3

2

If you're using Confluent Platform 3.3, I would recommend using Confluent CLI since it's part of the download you've already got and makes life much simpler. Then you can easily check the status of the components. 

confluent start
confluent status kafka

etc

Check out this vid here: https://vimeo.com/228505612

In terms of the issue you've got, I would check the log for Schema Registry. You can do that with Confluent CLI

confluent log schema-registry
Robin Moffatt
  • 30,382
  • 3
  • 65
  • 92
2

I also seen same issue while running the producer with Spring Cloud Stream. Replacing the localhost with actual IP address will help

satish chandra Shukla
  • 21
  • 1
  • Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Feb 20 '22 at 08:18
0

This might help someone, l faced a similar issue. The solution that worked for me was to change localhost in my connector settings (in my schema.registry.url) and replace it with the ip address of of the container for/running schema registry and it worked. For example

l had set it up like below:

"value.converter.schema.registry.url": "http://localhost:8081"
"key.converter.schema.registry.url": "http://localhost:8081"

and l changed it to the following

"value.converter.schema.registry.url": "http://172.19.0.4:8081",
 "key.converter.schema.registry.url": "http://172.19.0.4:8081"
LUNATIC
  • 21
  • 5