[
https://issues.apache.org/jira/browse/KAFKA-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606813#comment-16606813
]
Seweryn Habdank-Wojewodzki edited comment on KAFKA-6699 at 9/7/18 7:57 AM:
---------------------------------------------------------------------------
OK. Misunderstanding.
We have replication factor 2. And in topic _describe _I see Isr: 1,2. I am
still sure, we do not have wrong configuration.
And if, we would have, such a simple check like consistency between replication
factor and number of brokers, shall be as warning in client startup reported.
was (Author: habdank):
OK. Misunderstanding.
We have replication factor 2. And in topic describe I see Isr: 1,2. I am still
sure, we do not have wrong configuration.
And if, we would have, such a simple check like consistency between replication
factor and number of brokers, shall be as warning in client startup reported.
> 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)
