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 11:02:00 GMT

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

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

[~habdank] have you tried to specify a different application.id when it happens? As far as
I understand, it is used to determine underlying consumer group id. I suppose if the consumer
group coordinator is selected to be a node that is down, your streaming app can't process
anything. 

What do you see in the logs? Can you enable debug logging for your streaming application?
Do you see messages like the following? 
{code:java}
2018-03-23 11:58:38 DEBUG AbstractCoordinator:183 - [Consumer clientId=1-c69561f2-11f9-4d59-9c07-517d2f3d6313-StreamThread-1-consumer,
groupId=1] Group coordinator lookup failed: The coordinator is not available.{code}
 

> 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