question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Version 2.4.1 giving topic "not present in metadata after 60000 ms"

See original GitHub issue

After upgrading to embedded-kafka 2.4.1 (as well as upgrading the kafka client to the same version) we are seeing error such as:

Topic anytopic not present in metadata after 60000 ms

If we keep the kafka client at 2.4.1 and switch embedded-kafka back to 2.4.0 we do not see the error.

We are using withRunningKafka to start embedded kafka, but have tried to explicitly start/stop to no avail. We are using default configuration.

Scala version: 2.12.8 SBT version: 1.3.9 Kafka client version: 2.4.1 embedded kafka version: 2.4.1

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
francescopellegrinicommented, Apr 14, 2020

Found it: in 47f54c9 Kafka and Zookeeper default ports have been swapped, so now Kafka listens on port 6000 instead of 6001.

You can either:

  • update the port in your tests, or
  • provide an implicit EmbeddedKafkaConfig from which you’d read the actual port instead of hard-coding it in the Properties. 😃

Sorry about this, I might consider releasing a patched 2.4.1.1 version (and update embedded-kafka-schema-registry as well)…

0reactions
kbreidenbachcommented, Apr 14, 2020

Thanks for finding that so quickly!

Read more comments on GitHub >

github_iconTop Results From Across the Web

org.apache.kafka.common.errors.TimeoutException: Topic not ...
TimeoutException: Topic testtopic2 not present in metadata after 60000 ms. When trying to produce to the topic in my local kafka instance on ......
Read more >
Troubleshooting Error "Topic {{topic_name}} not present in ...
For a Kafka instance deployed in multiple AZs, if one of the AZs is faulty, error message "Topic {{topic_name}} not present in metadata...
Read more >
spring-projects/spring-kafka - Gitter
Topic badTopic not present in metadata after 60000 ms. . The producer keeps retrying up to max.block.ms . If I reduce it, I...
Read more >
Topic <topic-name> not present in metadata after 60000 ms ...
The error occurs when the ICDx forwarder tries to connect to Kafka but cannot read the Topic response before the timeout period.
Read more >
Error: Topic XXXX not present in metadata after 60000 ms
hello everyone, am having a problem that occurs randomly at the time when a producer tries to generate messages to any topic, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found