[
https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854956#comment-15854956
]
Sagar Sadashiv Patwardhan commented on KAFKA-4739:
--------------------------------------------------
[~hachikuji] I am with Vipul Singh. Is there a limit(timeout or number of
attempts) on how many times kafka client tries to reconnect to the broker? We
run into situations where a kafka client acquires multiple partitions but does
not read any messages due to this issue. It would be great if kafka client
could crash(or at least revoke the acquired partitions in case of prolonged
network connection issues) after x number of attempts or some timeout. We run
multiple consumers, and the other consumers read the messages without any issue
from this broker(partition(s)).
> 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)
