[
https://issues.apache.org/jira/browse/KAFKA-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771574#comment-13771574
]
Sriram Subramanian commented on KAFKA-1043:
-------------------------------------------
We no longer block on the socket buffers if they get full. We do block on a
slow I/O. That can be fixed by either capping it based on time or only fetching
a subset of topics. Even if there is no slow I/O and the socket buffers do not
get full, we could spend too much time processing the fetch response. In that
case, fetching only a subset of topics should help. Anything more is just over
engineering to me.
> Time-consuming FetchRequest could block other request in the response queue
> ---------------------------------------------------------------------------
>
> Key: KAFKA-1043
> URL: https://issues.apache.org/jira/browse/KAFKA-1043
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.1
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
> Fix For: 0.8, 0.8.1
>
>
> Since in SocketServer the processor who takes any request is also responsible
> for writing the response for that request, we make each processor owning its
> own response queue. If a FetchRequest takes irregularly long time to write
> the channel buffer it would block all other responses in the queue.
--
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
