[
https://issues.apache.org/jira/browse/KAFKA-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876487#comment-15876487
]
Colin P. McCabe commented on KAFKA-1935:
----------------------------------------
In the past, people expressed concerns about the number of sockets that Kafka
was using. Someone even proposed sharing the same NetworkClient between
producers and consumers in the same process, to avoid opening multiple sockets
to the same nodes. If this is a concern, perhaps what we need is to be able to
send more than one message at a time on a socket?
Another approach would be to change the key to be something more complex than a
string, and use something like a class that contained a node id and a string
role.
> Consumer should use a separate socket for Coordinator connection
> ----------------------------------------------------------------
>
> Key: KAFKA-1935
> URL: https://issues.apache.org/jira/browse/KAFKA-1935
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Guozhang Wang
> Labels: newbie
>
> KAFKA-1925 is just a quick-fix of this issue, we need to let consumer to be
> able to create separate sockets for the same server for coordinator / broker
> roles.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
