-
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
Multiple consumers with same group id get same message #112
Comments
That contract of one message per consumer group only works for the coordinated consumers which are implemented for the JVM only (i.e., Scala and Java clients). Kafka will eventually have better support for non-JVM clients to handle coordinated consumption at which point we'll implement this functionality. HTH |
Hi Mumrah - we're using this with storm and want to use storm's parallelization (all storm spouts will be in the same consumer group for a topic). Do you know if this is possible to do through this ? |
Can you configure them to pull from a single partition? If so, yes. If not, no. There is a pull request which looks like it will provide that functionality once Kafka server 0.8.2 goes live.
|
Link to this PR : #164 |
Is #164 still the answer for this one? Looks like it is still open / possibly abandoned. @wizzat is it expected to work out of the box on a single partition? I'll test it out, just wondering what the expected behavior is. This is pretty important for my team, so if there's no working solution yet I may take a shot at adding this |
It seems #164 was closed with "it was fixed with other commits" -- is that the case? We're still not seeing consumer balancing with kafka-python. |
Oh, it seems this will be implemented in #38 -- this is a dupe of that, basically. |
yes, #38 is the tracking issue. consumer rebalancing will be supported when using kafka brokers >= v0.9.0.0 . Development is on the 0.9 git branch. |
All my consumer with same group are getting all the same messages from all the producers. |
Kafka manual says that each message is delivered exactly to one consumer from a group (with a same group id). And this is what I see with Java high-level API and expected to see with Python's
SimpleConsumer
. However, when I run 2 consumers simultaneously (see code below) and send new message, both instances of consumer receive it.Note, that
auto_commit
in consumer is set toFalse
to overcome problem with Kafka 0.8.1 and current version of kafka-python, but changing it to True only adds exceptions and doesn't fix consumption problem.The text was updated successfully, but these errors were encountered: