You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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, wherekafka-rust
can do much better.In particular - in the scope of this ticket - we'd like
Producer
andConsumer
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.
The text was updated successfully, but these errors were encountered: