You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Seweryn Habdank-Wojewodzki (JIRA)" <ji...@apache.org> on 2018/03/21 09:36:00 UTC

[jira] [Created] (KAFKA-6699) When one of two Kafka nodes are dead, streaming API cannot handle messaging

Seweryn Habdank-Wojewodzki created KAFKA-6699:
-------------------------------------------------

             Summary: 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


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)