You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/02/03 08:37:00 UTC

[jira] [Updated] (ZOOKEEPER-3712) Add setKeepAlive support for NIOServerCnxn

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated ZOOKEEPER-3712:
--------------------------------------
    Labels: pull-request-available  (was: )

> 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
>            Priority: Major
>              Labels: pull-request-available
>
> 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)