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

Handle broker outage #81

Open
xitep opened this issue Feb 18, 2016 · 2 comments
Open

Handle broker outage #81

xitep opened this issue Feb 18, 2016 · 2 comments
Labels

Comments

@xitep
Copy link
Collaborator

xitep commented Feb 18, 2016

kafka-rust currently does a poor job of handling errors. It basically pushes all the responsibility to client code. However, that client code's only option, is to reload metadata and to try the operation again. There are various situations, though, where kafka-rust can do much better.

In particular - in the scope of this ticket - we'd like Producer and Consumer to try to "survive" the outage of a particular kafka broker in a cluster. In other words, the two clients shall transparently deal with partition leader re-assignment and temporary kafka errors.

More details to come.

@xitep xitep added the feature label Mar 1, 2016
@thijsc
Copy link
Contributor

thijsc commented Jun 7, 2016

Any progress on this one?

@xitep
Copy link
Collaborator Author

xitep commented Jun 8, 2016

unfortunately, no. not that i'm aware of. feel free to tackle this one. my focus is currently rather on #63.

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

No branches or pull requests

2 participants