[
https://issues.apache.org/jira/browse/KAFKA-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771528#comment-13771528
]
Guozhang Wang commented on KAFKA-1043:
--------------------------------------
Giving it some more thought, I think a long term fix should be decoupling the
sockets with the network threads. With this decoupling given a response and its
corresponding target socket, any network threads can then pick it up and write
it to socket. In this way we would have a network threads pool AND a socket
pool and any thread can work on any socket.
Any comments [~jkreps]?
> 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
