Neha Narkhede created KAFKA-665:
-----------------------------------
Summary: Outgoing responses delayed on a busy Kafka broker
Key: KAFKA-665
URL: https://issues.apache.org/jira/browse/KAFKA-665
Project: Kafka
Issue Type: Bug
Affects Versions: 0.8
Reporter: Neha Narkhede
Priority: Critical
Fix For: 0.8
In a long running test, I observed that after a few hours of operation, few
requests start timing out, mainly because they spent very long time sitting in
the response queue -
[2012-12-07 22:05:56,670] TRACE Completed request with correlation id 3965966
and client : TopicMetadataRequest:4009, queueTime:1, localTime:28,
remoteTime:0, sendTime:3980 (kafka.network.RequestChannel$)
[2012-12-07 22:04:12,046] TRACE Completed request with correlation id 3962561
and client : TopicMetadataRequest:3449, queueTime:0, localTime:29,
remoteTime:0, sendTime:3420 (kafka.network.RequestChannel$)
[2012-12-07 22:05:56,670] TRACE Completed request with correlation id 3965966
and client : TopicMetadataRequest:4009, queueTime:1, localTime:28,
remoteTime:0, sendTime:3980 (kafka.network.RequestChannel$)
We might have a problem in the way we process outgoing responses. Basically, if
the processor thread blocks on enqueuing requests in the request queue, it
doesn't come around to processing its responses which are ready to go out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
