kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Panos Skianis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing
Date Thu, 20 Jul 2017 01:22:00 GMT

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

Panos Skianis commented on KAFKA-5611:

I am wondering if this is related actually to https://issues.apache.org/jira/browse/KAFKA-5016
but I am not sure if the scenarios match 100% yet and at the moment
eg 5016 mentions 2 consumers run sequentially with the second one blocking whilst this one
refers to three of them running concurrently 

> One or more consumers in a consumer-group stop consuming after rebalancing
> --------------------------------------------------------------------------
>                 Key: KAFKA-5611
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5611
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions:
>            Reporter: Panos Skianis
>         Attachments: kka02, Server 1, Server 2, Server 3
> Scenario: 
>   - 3 zookeepers, 4 Kafkas., with 0.9.0 compatibility still on (other apps need
it but the one mentioned below is already on kafka  client).
>   - 3 servers running 1 consumer each under the same consumer groupId. 
>   - Servers seem to be consuming messages happily but then there is a timeout to an external
service that causes our app to restart the Kafka Consumer on one of the servers (this is by
design). That causes rebalancing of the group and upon restart of one of the Consumers seem
to "block".
>   - Server 3 is where the problems occur.
>   - Problem fixes itself either by restarting one of the 3 servers or cause the group
to rebalance again by using the console consumer with the autocommit set to false and using
the same group.
> Note: 
>  - Haven't managed to recreate it at will yet.
>  - Mainly happens in production environment, often enough. Hence I do not have any logs
with DEBUG/TRACE statements yet.
>  - Extracts from log of each app server are attached. Also the log of the kafka that
seems to be dealing with the related group and generations.
>  - See COMMENT lines in the files for further info.

This message was sent by Atlassian JIRA

View raw message