[
https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117638#comment-14117638
]
nicu marasoiu edited comment on KAFKA-1282 at 9/1/14 7:46 PM:
--------------------------------------------------------------
I am sorry, Yes, that was the intent! I will write unit tests from now on to
avoid such slips.
Moreover, the removeEldestEntry will return false all the time, because it
keeps the responsability of mutating the map for itself, as part of calling the
close method.
Attached, running tests now.
was (Author: nmarasoi):
I am sorry, Yes, that was the intent! I will write unit tests from now on to
avoid such slips.
Moreover, the removeEldestEntry will return false all the time, because it
keeps the responsability of mutating the map for itself, as part of calling the
close method.
Attached, but I am not able to test the patch, because any scala version I use
for the test task, it remains blocked at: Building 87% > :test_core_2_9_1 >
:kafka:core:test
> 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,
> idleDisconnect.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)
