Skip to content
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

Does kafka-python support broker rebalancing? #269

Closed
ddieterly opened this issue Nov 26, 2014 · 2 comments
Closed

Does kafka-python support broker rebalancing? #269

ddieterly opened this issue Nov 26, 2014 · 2 comments

Comments

@ddieterly
Copy link

I understand that kafka-python does not do consumer rebalancing (consumer failover) when consumers come and go. That has been made clear by other discussion threads. How does kafka-python handle broker rebalancing? Does it handle broker rebalancing?

From https://cwiki.apache.org/confluence/display/KAFKA/Consumer+Client+Re-Design we see that the high-level Java Consumers do the following:

  1. Auto/Hidden Offset Management
  2. Auto(Simple) Partition Assignment
  3. Broker Failover => Auto Rebalance
  4. Consumer Failover => Auto Rebalance

We know that kafka-python does not do #4, the consumer failover. Which of the others does kafka-python handle? Or conversely, which of the others does kakfa-python not handle? It appears to be handling #1 but none of the others. Can we get confirmation on that?

Thanks.

@wizzat
Copy link
Collaborator

wizzat commented Nov 26, 2014

2, 3, and 4 are all variations on the same topic: how to automatically split partitions amongst different consumers in various cases. You are correct: this is not natively supported in the python client.

@wizzat wizzat closed this as completed Nov 26, 2014
@jyotidhiman0610
Copy link

jyotidhiman0610 commented Jun 13, 2018

What's the ideal solution when one of the brokers goes down?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants