You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2018/09/12 17:14:00 UTC
[jira] [Resolved] (KAFKA-6699) When one of two Kafka nodes are
dead, streaming API cannot handle messaging
[ https://issues.apache.org/jira/browse/KAFKA-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias J. Sax resolved KAFKA-6699.
------------------------------------
Resolution: Not A Bug
This ticket does not seem to be a bug but a configuration question. I am closing this for now. If you have further questions, please consult the user mailing list (https://kafka.apache.org/contact).
> 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)