[
https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098324#comment-14098324
]
Nicolae Marasoiu commented on KAFKA-1282:
-----------------------------------------
Hi, I am sorry, but traversing will be limited to the connections that will
actually be expired, so there is no traversing of non-expiring connections!
Say the server hold 100K connections. Say 100 connections are not used in the
last 10 minutes.
What the program does (or I will make sure it does) is just iterate through the
first 101 connections, the first 100 will be expired and it will stop at number
101.
I think this is an exact achievement of expected behavior of the jira task, as
intended, and there is no performance penalty to that really!
> 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)
