kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing
Date Tue, 25 Jul 2017 05:45:00 GMT

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

ASF GitHub Bot commented on KAFKA-5611:
---------------------------------------

GitHub user hachikuji opened a pull request:

    https://github.com/apache/kafka/pull/3571

    KAFKA-5611; AbstractCoordinator should handle wakeup raised from onJoinComplete

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/hachikuji/kafka KAFKA-5611

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/3571.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3571
    
----
commit e0b4f65031dbb8135d872811c68dec94f7a45efd
Author: Jason Gustafson <jason@confluent.io>
Date:   2017-07-25T05:14:42Z

    KAFKA-5611; AbstractCoordinator should handle wakeup raised from onJoinComplete

----


> 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: 0.10.2.0
>            Reporter: Panos Skianis
>            Assignee: Jason Gustafson
>         Attachments: bad-server-with-more-logging-1.tar.gz, kka02, Server 1, Server 2,
Server 3
>
>
> Scenario: 
>   - 3 zookeepers, 4 Kafkas. 0.10.2.0, with 0.9.0 compatibility still on (other apps need
it but the one mentioned below is already on kafka 0.10.2.0  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
(v6.4.14#64029)

Mime
View raw message