[
https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105606#comment-14105606
]
nicu marasoiu commented on KAFKA-1282:
--------------------------------------
After discussion with Neha, we agreed that using the removeEldestEntry approach
works better in the sense that avoids disruption caused by potentially many
connections being up for close at once, and evens out that overhead. The
disadvantage remains that an inactive server will not close connections but
seems less than the advantage of closing overhead leveling and of performance
plus of not traversing and of not polling the oldest entry.
> 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
> Assignee: Neha Narkhede
> Labels: newbie++
> Fix For: 0.9.0
>
> Attachments:
> kafka-1282__Disconnect_idle_socket_connection_in_Selector.patch
>
>
> 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)
