[
https://issues.apache.org/jira/browse/ZOOKEEPER-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Han resolved ZOOKEEPER-3712.
------------------------------------
Fix Version/s: 3.6.1
Resolution: Fixed
Issue resolved by pull request 1242
[https://github.com/apache/zookeeper/pull/1242]
> Add setKeepAlive support for NIOServerCnxn
> ------------------------------------------
>
> Key: ZOOKEEPER-3712
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3712
> Project: ZooKeeper
> Issue Type: New Feature
> Components: server
> Affects Versions: 3.6.0, 3.4.14, 3.5.6
> Reporter: Pierre Yin
> Assignee: Pierre Yin
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.6.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Suggest to add setKeepAlive support for NIOServerCnxn. It can resolve some
> tcp connection leak issue caused by network broken. In some occasional
> case(network switcher broken, network card broken, iptables firewall strategy
> and so on....), zookeeper server would lose the FIN packet when the client
> close the connection. In such scenario, the connection will be treated as
> alive forever and never be closed.
> These leaked tcp connections introduce the resource leak risk.
> setKeepAlive for every client NIO connection can prevent the resource leak
> risk.
>
> I will send the patch later. Hope someone can help to review it.
> Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
