Skip to content

ReplicaNotAvailable can be safely ignored#88

Open
arturmkrtchyan wants to merge 1 commit into
bpot:masterfrom
arturmkrtchyan:master
Open

ReplicaNotAvailable can be safely ignored#88
arturmkrtchyan wants to merge 1 commit into
bpot:masterfrom
arturmkrtchyan:master

Conversation

@arturmkrtchyan

Copy link
Copy Markdown

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

coveralls commented May 29, 2015

Copy link
Copy Markdown

Coverage Status

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

@arturmkrtchyan

Copy link
Copy Markdown
Author

@bpot when can you get this merged?

@arturmkrtchyan

Copy link
Copy Markdown
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 <
notifications@github.com> 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
Copy Markdown

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

@GEverding

Copy link
Copy Markdown

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

@fegoa89

fegoa89 commented Jul 6, 2015

Copy link
Copy Markdown

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