[ https://issues.apache.org/jira/browse/KAFKA-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612356#comment-16612356 ]
Seweryn Habdank-Wojewodzki edited comment on KAFKA-6699 at 9/12/18 3:40 PM: ---------------------------------------------------------------------------- [~mjsax]I understand you point, but still I do not see why we need more than 2 kafka brokers. Especially that we have 5 separated zookeeper nodes. And our setup was reviewed by someone from Confluent - I do not remember by whom. was (Author: habdank): [~mjsax]I understand you point, but still I do not see why we need more than 2 kafka brokers. Especially that we have 5 separate zookeeper nodes. And our setup was reviewed by someone from Confluent - I do not remember by whom. > When one of two Kafka nodes are dead, streaming API cannot handle messaging > --------------------------------------------------------------------------- > > Key: KAFKA-6699 > URL: https://issues.apache.org/jira/browse/KAFKA-6699 > Project: Kafka > Issue Type: Bug > Components: streams > Affects Versions: 0.11.0.2 > Reporter: Seweryn Habdank-Wojewodzki > Priority: Major > > Dears, > I am observing quite often, when Kafka Broker is partly dead(*), then > application, which uses streaming API are doing nothing. > (*) Partly dead in my case it means that one of two Kafka nodes are out of > order. > Especially when disk is full on one machine, then Broker is going in some > strange state, where streaming API goes vacations. It seems like regular > producer/consumer API has no problem in such a case. > Can you have a look on that matter? -- This message was sent by Atlassian JIRA (v7.6.3#76005)