[
https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-1282.
----------------------------
Resolution: Fixed
Fix Version/s: 0.9.0.0
[~nmarasoi], yes, the actual problem is now fixed in trunk. We just need to add
a unit test. I created a followup jira KAFKA-2661 for that. Resolving this jira.
> 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.0
> Reporter: Jun Rao
> Assignee: nicu marasoiu
> Labels: newbie++
> Fix For: 0.9.0.0
>
> Attachments: 1282_access-order_+_test_(same_class).patch,
> KAFKA-1282_Disconnect_idle_socket_connection_in_Selector.patch,
> access-order_+_test.patch,
> access_order_+_test_waiting_from_350ms_to_1100ms.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.3.4#6332)
