[
https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066315#comment-14066315
]
Nicolae Marasoiu commented on KAFKA-1282:
-----------------------------------------
Right, the limitation is more critical on the client side of a client-server
connection due to port count limitation, and/or socket/file count restrictions
of the client env.
On the other hand, the brokers could close the connections too on such
condition, rather than relying on the clients(producers) to protect it.
However, what is any other reason to reduce the socket connections count? To
make the NIO select lighter on the server, on a lesser number of connections? I
think epoll is quite relaxed on this.
I would like to work on this, but also understand the original problem(s) /
concern(s) to see if we can also see any more suitable solutions to the
particular concern?
> Disconnect idle socket connection in Selector
> ---------------------------------------------
>
> Key: KAFKA-1282
> URL: https://issues.apache.org/jira/browse/KAFKA-1282
> Project: Kafka
> Issue Type: Bug
> Components: producer
> Affects Versions: 0.8.2
> Reporter: Jun Rao
> Labels: newbie++
> Fix For: 0.9.0
>
>
> To reduce # socket connections, it would be useful for the new producer to
> close socket connections that are idle. We can introduce a new producer
> config for the idle time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
