You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Panos Skianis (JIRA)" <ji...@apache.org> on 2017/07/20 01:14:00 UTC
[jira] [Updated] (KAFKA-5611) One or more consumers in a
consumer-group stop consuming after rebalancing
[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Panos Skianis updated KAFKA-5611:
---------------------------------
Description:
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.
was:
Scenario:
- 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.
> 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
> Attachments: 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)