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

["Seweryn Habdank-Wojewodzki (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411274#comment-16411274 ] 

Seweryn Habdank-Wojewodzki edited comment on KAFKA-6699 at 3/23/18 11:54 AM:
-----------------------------------------------------------------------------

[~astubbs] Replication factor is 2. Topic has as well 10 partitions.

[~asasvari] I will try to re-test this case with DEBUG logs on streamming API level, but it will take me some time.


was (Author: habdank):
[~astubbs]Replication factor is 2. Topic has as well 10 partitions.
[~asasvari]I will try to re-test this case with DEBUG logs on streamming API level, but it will take me some time.

> 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)