kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Attila Sasvari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6699) When one of two Kafka nodes are dead, streaming API cannot handle messaging
Date Fri, 23 Mar 2018 14:24:00 GMT

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

Attila Sasvari commented on KAFKA-6699:
---------------------------------------

[~habdank] just a quick question: is the replication factor set to 2 for the internal topic
{{__consumer_offsets}} too? Please note if you change the application id, you will not be
able to continue consuming messages from the last processed offset (unless you do some magic). 

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

Mime
View raw message