[
https://issues.apache.org/jira/browse/KAFKA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137796#comment-14137796
]
nicu marasoiu edited comment on KAFKA-1282 at 9/18/14 5:12 AM:
---------------------------------------------------------------
Indeed, ack=1 solves it, it gets a reset by peer and a socket timeout on fetch
meta, than re connects and sends message.
[~jkreps], [~nehanarkhede], [~junrao], please let me know any feedback on my
last uploaded patch, it should be ok I think
was (Author: nmarasoi):
Indeed, ack=1 solves it, it gets a reset by peer and a socket timeout on fetch
meta, than re connects and sends message.
> 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: nicu marasoiu
> Labels: newbie++
> Fix For: 0.9.0
>
> Attachments: 1282_brushed_up.patch,
> 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.3.4#6332)
