-
Notifications
You must be signed in to change notification settings - Fork 102
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 not handle a single down broker #104
Comments
Oddly enough, it also does not send to broker2 at all, although other clients can which are written in C++ or Java. |
|
See #105 for a fix for this. |
@skandragon |
I'm not sure what you mean here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have two brokers, and am configuring a partition producer as such:
I am getting this error when broker1 is down:
end
Any idea how to make this resilient against a broker being down?
The text was updated successfully, but these errors were encountered: