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

Consider getting rid of zookeeper as a coordinator #281

Open
michal-harish opened this issue Oct 16, 2019 · 1 comment
Open

Consider getting rid of zookeeper as a coordinator #281

michal-harish opened this issue Oct 16, 2019 · 1 comment

Comments

@michal-harish
Copy link
Member

michal-harish commented Oct 16, 2019

The purpose of the coordinator is to allow nodes to come online and offline dynamically. This is achieved by the following 3 functions:

  1. inform about nodes coming online/offline and mediate their addresses to each other
  2. generate assignment for each keyspace based on required replication factor and a state of previous assignment (to move as few partitions as possible)
  3. elect leaders for online replicas of the same partition
@michal-harish
Copy link
Member Author

this could be done by a combination of gossip/raft and single-partition kafka topic

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

No branches or pull requests

1 participant