search

SOHU-Co / kafka-node

Node.js client for Apache Kafka 0.8 and later.
MIT License
2.66k stars 628 forks source link

Error: missing handlers for Correlation ID #808

Open sumitjainn opened 6 years ago

sumitjainn commented 6 years ago

I am getting these errors while using ConsumerGroup. They come after running the app for some time (1 day or two) and afterwards consumer stops receiving any messages.

"error: missing handlers for Correlation ID: 1506"

kafka version: 0.10 kafka-node version: 2.2.3

hyperlink commented 6 years ago

any other log or errors that happens before or after this?

sumitjainn commented 6 years ago

No, there are no other errors apart from this

hyperlink commented 6 years ago

Does this happen with consumerGroup connected using zookeeper host?

sumitjainn commented 6 years ago

No.. they are connected through kafka brokerString

hyperlink commented 6 years ago

My last message wasn't clear. There are some differences between the clients I wonder if this issue still happens if you were to use the zookeeper based Client. To do that you can connect to the broker through the zookeeper host.

sumitjainn commented 6 years ago

But that would lose the consumer offsets stored in __consumer_offsets topic, right?

hyperlink commented 6 years ago

Don't worry, the offsets are still stored in kafka. Zookeeper is only used for broker discovery. KafkaClient overrides some methods so I wonder if those overrides are causing some issues.

sumitjainn commented 6 years ago

Sure, will give it a try.. but It will also do away with socket error retries and recovery.

hyperlink commented 6 years ago

Are you still getting this error with the latest version?

ajwootto commented 5 years ago

I have just started receiving these errors as well. It seems to be related to rebalancing and heartbeat request failures. Around the same time I see things like:

{"message":"Kafka Error Code: 27","errorCode":27}

For the heartbeat error, as well as a bunch of these:

 Connect ignored. Currently connecting.

The latter error seems to occur a ton in quick succession (like hundreds of times in the span of a millisecond).