-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KAFKA-3177: consumer hangs when assigned to partition that doesn't exist #686
Comments
See https://issues.apache.org/jira/browse/KAFKA-3177 -- I will follow whatever fix the apache client lands on. For now, it's a known issue. Also, the Kafka broker error is unrelated (this is because kafka-python attempts to ping various apis to determine the broker version... API 16 is a new api only available on 0.10). |
@sibiryakov late, yes, but one way around this is to check if a partition exists for a topic before trying to poll or do anything with it. use the |
Will this apply to Not sure what level the problem manifests, and I know both |
@jefwidman, from a quick look at the code, it doesn't seem so. I don't see a way to get the partitions for a topic using the |
Patch Set 1: Some of the issues I'm concerned about: dpkp/kafka-python#674 dpkp/kafka-python#686 dpkp/kafka-python#579 dpkp/kafka-python#551 Patch-set: 1
Hi guys,
the code below doesn't work. I'm probably doing something wrong, but I couldn't make it to work.
Kafka-python version is 1.1.1
and Kafka is 0.8.2.2.
Kafka broker output
[2016-05-11 14:46:14,669] ERROR Closing socket for /0:0:0:0:0:0:0:1 because of error (kafka.network.Processor) kafka.common.KafkaException: Wrong request type 16 at kafka.api.RequestKeys$.deserializerForKey(RequestKeys.scala:64) at kafka.network.RequestChannel$Request.<init>(RequestChannel.scala:50) at kafka.network.Processor.read(SocketServer.scala:450) at kafka.network.Processor.run(SocketServer.scala:340) at java.lang.Thread.run(Thread.java:745)
Traceback on KeyboardInterrupt
It certainly shouldn't hang, instead raise an exception.
The text was updated successfully, but these errors were encountered: