Tommy Brunn

> I'm following the guide at to handle error in my consumer, trying to stop consuming the messages. What guide is this? Typically you don't pause and resume consumers because...

Pausing and resuming should work, yes, but it's not the right tool to use for processing a message async. All you need to do is not resolve the handler: ```js...

Exactly-once is a very misunderstood topic. When Confluent says that Kafka supports exactly-once semantics, they mean that in the sense that the _observable outcome_ of a topic being processed is...

This is an issue of distributed systems - whether there's an API for being notified or not doesn't matter. The member won't know at that time that there is a...

To have a chance to debug this, you need to provide some information: 1. What version of KafkaJS are you using? 2. What version of Kafka are you running? 3....

If you run KafkaJS with the [log level set to debug](https://kafka.js.org/docs/configuration#logging) you can see each request the client makes towards the broker, including heartbeats, which can help you confirm or...

You are correct that heartbeats should be sent even when there are no messages, but this is done internally by KafkaJS. Somewhat simplified, it essentially has a loop where it...

You can't do that in KafkaJS itself. Fetching from Kafka happens in numbers of bytes, not messages. So there's no way we can ask the broker for X number of...

@vikashhrs Please don't derail this issue with unrelated comments. Your question is better suited for the NestJS support channels rather than KafkaJS.

@WaleedAshraf describes the expected experience. The way that Kafka clients work is that they initially connect to one broker, and then discover the rest of the cluster. In case it...