[
https://issues.apache.org/jira/browse/KAFKA-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871619#comment-15871619
]
Narendra Kumar commented on KAFKA-4676:
---------------------------------------
We are also facing the same issue.
[~onurkaraman] :
We are seeing this line quite frequently in consumer logs:
log.debug("Disconnecting from node {} due to request timeout.", nodeId);
What does it mean , is it related to broker being busy with something else like
GC?
> Kafka consumers gets stuck for some partitions
> ----------------------------------------------
>
> Key: KAFKA-4676
> URL: https://issues.apache.org/jira/browse/KAFKA-4676
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.1.0
> Reporter: Vishal Shukla
> Priority: Critical
> Labels: consumer, reliability
> Attachments: restart-node2-consumer-node-1.log,
> restart-node2-consumer-node-2.log, stuck-case2.log,
> stuck-consumer-node-1.log, stuck-consumer-node-2.log,
> stuck-topic-thread-dump.log
>
>
> We recently upgraded to Kafka 0.10.1.0. We are frequently facing issue that
> Kafka consumers get stuck suddenly for some partitions.
> Attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
