You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 13, 2019. It is now read-only.
The issue I'm running into is on our local development boxes, I'd like to handle the situation where the partitions are not yet set up for a Kafka topic:
[Sarama] 2015/03/12 18:11:25 [consumer/a0103be9d1f2] Currently registered consumers: 1
[Sarama] 2015/03/12 18:11:25 [consumer/a0103be9d1f2] session :: Started topic consumer
[Sarama] 2015/03/12 18:11:25 [consumer/a0103be9d1f2] session :: FAILED to get list of partitions: zk: node does not exist
I believe that is saying that it's registering the consumer, but zookeeper doesn't know about the partitions for the topic. Unfortunately it seems to print this message to the stdout log and continue on. There don't appear to be any messages in any error channels or any errors coming back as this is returned form a go routine.
It would be great to detect if this scenario has occurred, and be able to handle the case where my consumers come up before topics and partitions are created (for local development with docker in particular).
The text was updated successfully, but these errors were encountered:
The issue I'm running into is on our local development boxes, I'd like to handle the situation where the partitions are not yet set up for a Kafka topic:
I believe that is saying that it's registering the consumer, but zookeeper doesn't know about the partitions for the topic. Unfortunately it seems to print this message to the stdout log and continue on. There don't appear to be any messages in any error channels or any errors coming back as this is returned form a go routine.
It would be great to detect if this scenario has occurred, and be able to handle the case where my consumers come up before topics and partitions are created (for local development with docker in particular).
The text was updated successfully, but these errors were encountered: