[
https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860768#comment-15860768
]
Jason Gustafson commented on KAFKA-4739:
----------------------------------------
[~neoeahit] Thanks for the update. These logs look much more like what I
expect. There doesn't appear to be anything wrong with the consumer, but it
would be nice to confirm it.
1. Can you use the console consumer both with and without the
{{--new-consumer}} option to consume from the same exact topics?
2. You mentioned that you can reproduce the problem by restarting the process
repeatedly, can you explain this a bit more? Can you get the same behavior
using the console consumer?
3. If you can get the consumer into this state again, can you get a thread dump
from the broker? There have been a couple deadlocks fixed since 0.9.0.1, so it
would be nice to confirm that we're not hitting one of them.
4. What do you do currently to recover? Since you said restarting the consumers
doesn't help, what does? Restarting the brokers?
> KafkaConsumer poll going into an infinite loop
> ----------------------------------------------
>
> Key: KAFKA-4739
> URL: https://issues.apache.org/jira/browse/KAFKA-4739
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 0.9.0.1
> Reporter: Vipul Singh
>
> We are seeing an issue with our kafka consumer where it seems to go into an
> infinite loop while polling, trying to fetch data from kafka. We are seeing
> the heartbeat requests on the broker from the consumer, but nothing else from
> the kafka consumer.
> We enabled debug level logging on the consumer, and see these logs:
> https://gist.github.com/neoeahit/757bff7acdea62656f065f4dcb8974b4
> And this just goes on. The way we have been able to replicate this issue, is
> by restarting the process in multiple successions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
