[
https://issues.apache.org/jira/browse/KAFKA-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966278#comment-15966278
]
Vahid Hashemian commented on KAFKA-5016:
----------------------------------------
[~domenico74] I have not been able to reproduce this issue with the 0.10.2.0
code base.
I tried this with command line producer and consumer, and also coded a simple
Jave based producer and consumer to run your use case.
Here's what I did:
* Ran a producer that writes 10 messages to a non-existing topic {{test}} (this
causes the topic {{test}} to be auto-created with a single partition)
* Ran a consumer that belongs to the consumer group {{cgroup}} and consumes
from the topic {{test}}
* Ran a second consumer similar to first one.
After this, when I run the consumer group command, I see this:
{code}
$ bin/kafka-consumer-groups.sh --bootstrap-server localhost:9092 --describe
--group cgroup
TOPIC PARTITION CURRENT-OFFSET LOG-END-OFFSET LAG CONSUMER-ID
HOST CLIENT-ID
test 0 10 10 0
consumer-1-1c06c568-7a83-42ea-a2d7-8a53132397bd /127.0.0.1 consumer-1
- - - - -
consumer-1-73aaff69-b43f-4be3-8b48-99bf337abc9a /127.0.0.1 consumer-1
{code}
I also don't see any issues in my server log:
{code}
...
[2017-04-12 10:35:57,976] INFO [Group Metadata Manager on Broker 0]: Finished
loading offsets from __consumer_offsets-42 in 1 milliseconds.
(kafka.coordinator.GroupMetadataManager)
[2017-04-12 10:35:57,976] INFO [Group Metadata Manager on Broker 0]: Loading
offsets and group metadata from __consumer_offsets-45
(kafka.coordinator.GroupMetadataManager)
[2017-04-12 10:35:57,977] INFO [Group Metadata Manager on Broker 0]: Finished
loading offsets from __consumer_offsets-45 in 1 milliseconds.
(kafka.coordinator.GroupMetadataManager)
[2017-04-12 10:35:57,977] INFO [Group Metadata Manager on Broker 0]: Loading
offsets and group metadata from __consumer_offsets-48
(kafka.coordinator.GroupMetadataManager)
[2017-04-12 10:35:57,978] INFO [Group Metadata Manager on Broker 0]: Finished
loading offsets from __consumer_offsets-48 in 1 milliseconds.
(kafka.coordinator.GroupMetadataManager)
[2017-04-12 10:35:57,984] INFO [GroupCoordinator 0]: Preparing to restabilize
group cgroup1 with old generation 0 (kafka.coordinator.GroupCoordinator)
[2017-04-12 10:35:57,987] INFO [GroupCoordinator 0]: Stabilized group cgroup1
generation 1 (kafka.coordinator.GroupCoordinator)
[2017-04-12 10:35:57,995] INFO [GroupCoordinator 0]: Assignment received from
leader for group cgroup1 for generation 1 (kafka.coordinator.GroupCoordinator)
[2017-04-12 10:36:10,624] INFO [GroupCoordinator 0]: Preparing to restabilize
group cgroup1 with old generation 1 (kafka.coordinator.GroupCoordinator)
[2017-04-12 10:36:13,116] INFO [GroupCoordinator 0]: Stabilized group cgroup1
generation 2 (kafka.coordinator.GroupCoordinator)
[2017-04-12 10:36:13,118] INFO [GroupCoordinator 0]: Assignment received from
leader for group cgroup1 for generation 2 (kafka.coordinator.GroupCoordinator)
{code}
Would you be able to share the code you are using that leads to the issue?
Thanks.
> Consumer hang in poll method while rebalancing is in progress
> -------------------------------------------------------------
>
> Key: KAFKA-5016
> URL: https://issues.apache.org/jira/browse/KAFKA-5016
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.10.1.0, 0.10.2.0
> Reporter: Domenico Di Giulio
> Assignee: Vahid Hashemian
> Attachments: Kafka 0.10.2.0 Issue (TRACE) - Server + Client.txt,
> Kafka 0.10.2.0 Issue (TRACE).txt
>
>
> After moving to Kafka 0.10.2.0, it looks like I'm experiencing a hang in the
> rebalancing code.
> This is a test case, not (still) production code. It does the following with
> a single-partition topic and two consumers in the same group:
> 1) a topic with one partition is forced to be created (auto-created)
> 2) a producer is used to write 10 messages
> 3) the first consumer reads all the messages and commits
> 4) the second consumer attempts a poll() and hangs indefinitely
> The same issue can't be found with 0.10.0.0.
> See the attached logs at TRACE level. Look for "SERVER HANGS" to see where
> the hang is found: when this happens, the client keeps failing any hearbeat
> attempt, as the rebalancing is in progress, and the poll method hangs
> indefinitely.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
