Skip to content

ReplicaNotAvailable can be safely ignored #88

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

arturmkrtchyan
Copy link

https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-ErrorCodes indicates that error 9 (ReplicaNotAvailable) can be safely ignored.

This fixes #86

@coveralls
Copy link

coveralls commented May 29, 2015

Coverage Status

Coverage increased (+1.7%) to 94.057% when pulling dbebae6 on arturmkrtchyan:master into dd74d94 on bpot:master.

@arturmkrtchyan
Copy link
Author

@bpot when can you get this merged?

@arturmkrtchyan
Copy link
Author

I just wander how others use this library without facing this issue. I have
an impression no one tested failure scenarios.

On Tue, Jun 23, 2015 at 4:18 PM, Krzysztof Jablonski <
[email protected]> wrote:

[image: 👍] this is real issue for my system where I have 4 servers and
ReplicationFactor set to 4. When one system is down Poseidon is not
available to send any message :(


Reply to this email directly or view it on GitHub
#88 (comment).

@infothrill
Copy link

Nice one! I'd love to see this in a released version.

@GEverding
Copy link

I fought with this issue yesterday! Can we get this into a new release?

@fegoa89
Copy link

fegoa89 commented Jul 6, 2015

Would be great to have it in a new release !

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

Successfully merging this pull request may close these issues.

Write to Kafka when loosing a Broker Connection
5 participants